GHSA-387m-935m-c4vw is a high-severity (CVSS 7.5) vulnerability in io.micronaut:micronaut-http-client. O3 Security confirms whether GHSA-387m-935m-c4vw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Micronaut doesn't set a maximum redirect count for its HTTP Client, enabling infinite loop DoS
Real-World Exposure
io.micronaut:micronaut-http-client☕io.micronaut:micronaut-http-client☕io.micronaut:micronaut-http-clientReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
The Netty-based Micronaut HTTP Client does not impose a limit on HTTP redirections, potentially allowing an infinite redirect loop that could lead to a denial-of-service attack.
Patches
The following versions are patched:
- For Micronaut 5, versions equal or greater than 5.0.1 >=
- For Micronaut 4, versions equal or greater than 4.10.24 >=
- For Micronaut 3, versions equal or greater than 3.10.7 >=
Workarounds
No
Resources
Micronaut 5 Patch: https://github.com/micronaut-projects/micronaut-core/commit/6e88a972718d6e1521c5b3bb7766451798dba4e3 Micronaut 4 Patch: https://github.com/micronaut-projects/micronaut-core/commit/f1dffffec8fb5e3b7e94ae907ce0be3831e499d4 Micronaut 3 Patch: https://github.com/micronaut-projects/micronaut-core/commit/c06a2715ca7f78321bc3ca05f41cca78cd351320
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.micronaut:micronaut-http-client | all versions | 3.10.7 |
| ☕Maven | io.micronaut:micronaut-http-client | ≥ 4.0.0-M1&&< 4.10.24 | 4.10.24 |
| ☕Maven | io.micronaut:micronaut-http-client | ≥ 5.0.0-M1&&< 5.0.1 | 5.0.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.micronaut:micronaut-http-client. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update io.micronaut:micronaut-http-client to 3.10.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-387m-935m-c4vw is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-387m-935m-c4vw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-387m-935m-c4vw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-387m-935m-c4vw in your dependencies?
O3 detects GHSA-387m-935m-c4vw across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.