Micronaut's HTTP client is vulnerable to HTTP Request Header InjectionGHSA-694p-xrhg-x3wm
CRITICALFix: micronaut-projects/micronaut-core@6deb60bGHSA-694p-xrhg-x3wm is a critical-severity (CVSS 9.8) CWE-444 vulnerability in io.micronaut:micronaut-http-client. 2 public exploit references exist, so weaponization risk is real. A fix is available for io.micronaut:micronaut-http-client — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-694p-xrhg-x3wm by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 384,189 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
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
Vulnerability
Micronaut's HTTP client is vulnerable to "HTTP Request Header Injection" due to not validating request headers passed to the client.
Example of vulnerable code:
@Controller("/hello")
public class HelloController {
@Inject
@Client("/")
RxHttpClient client;
@Get("/external-exploit")
@Produces(MediaType.TEXT_PLAIN)
public String externalExploit(@QueryValue("header-value") String headerValue) {
return client.toBlocking().retrieve(
HttpRequest.GET("/hello")
.header("Test", headerValue)
);
}
}
In the above case a query value received from a user is passed as a header value to the client. Since the client doesn't validate the header value the request headers and body have the potential to be manipulated.
For example, a user that supplies the following payload, can force the client to make multiple attacker-controlled HTTP requests.
List<String> headerData = List.of(
"Connection: Keep-Alive", // This keeps the connection open so another request can be stuffed in.
"",
"",
"POST /hello/super-secret HTTP/1.1",
"Host: 127.0.0.1",
"Content-Length: 31",
"",
"{\"new\":\"json\",\"content\":\"here\"}",
"",
""
);
String headerValue = "H\r\n" + String.join("\r\n", headerData);;
URI theURI =
UriBuilder
.of("/hello/external-exploit")
.queryParam("header-value", headerValue) // Automatically URL encodes data
.build();
HttpRequest<String> request = HttpRequest.GET(theURI);
String body = client.toBlocking().retrieve(request);
Note that using @HeaderValue instead of @QueryValue is not vulnerable since Micronaut's HTTP server does validate the headers passed to the server, so the exploit can only be triggered by using user data that is not an HTTP header (query values, form data etc.).
Impact
The attacker is able to control the entirety of the HTTP body for their custom requests. As such, this vulnerability enables attackers to perform a variant of Server Side Request Forgery.
Patches
The problem has been patched in the micronaut-http-client versions 1.2.11 and 1.3.2 and above.
Workarounds
Do not pass user data directly received from HTTP request parameters as headers in the HTTP client.
References
Fix commits
- https://github.com/micronaut-projects/micronaut-core/commit/9d1eff5c8df1d6cda1fe00ef046729b2a6abe7f1
- https://github.com/micronaut-projects/micronaut-core/commit/6deb60b75517f80c57b42d935f07955c773b766d
- https://github.com/micronaut-projects/micronaut-core/commit/bc855e439c4a5ced3d83195bb59d0679cbd95add
For more information
If you have any questions or comments about this advisory:
- Open an issue in micronaut-core
- Email us at [email protected]
Credit
Originally reported by @JLLeitschuh
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.micronaut:micronaut-http-client | all versions | 1.2.11io.micronaut:micronaut-http-client:1.2.11 |
| ☕Maven | io.micronaut:micronaut-http-client | ≥ 1.3.0&&< 1.3.2 | 1.3.2io.micronaut:micronaut-http-client:1.3.2 |
Affected Products
micronautobjectcomputingResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.micronaut:micronaut-http-client to 1.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-694p-xrhg-x3wm is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is GHSA-694p-xrhg-x3wm in your dependencies?
Find it across Maven, including transitive dependencies.