Vulnerability in io.micronaut:micronaut-http-client (CVE-2020-7611)
Summary
Vulnerability in io.micronaut:micronaut-http-client (CVE-2020-7611). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.3.2 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-7611 has been found in io.micronaut:micronaut-http-client.
Successful exploitation can lead to full system takeover.
What to do: upgrade io.micronaut:micronaut-http-client to 1.3.2 or later.
If unsure, ask your IT team or search "io.micronaut:micronaut-http-client CVE-2020-7611" on the vendor's site.
CVE-2020-7611 (io.micronaut:micronaut-http-client) — CWE-444
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.3.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-444) exists in io.micronaut:micronaut-http-client.
Check the vendor advisory for the affected versions of io.micronaut:micronaut-http-client.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 1.3.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで io.micronaut:micronaut-http-client を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade io.micronaut:micronaut-http-client to 1.3.2ステージング環境で 1.3.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- report snyk.io
- web github.com
- web github.com