Vulnerability in com.typesafe.akka:akka-http-core (CVE-2021-23339)
Summary
Vulnerability in com.typesafe.akka:akka-http-core (CVE-2021-23339). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 10.1.14 or later.
Original description
The description as published by the source.
A vulnerable Akka HTTP server will accept a malformed message and hand it over to the user. If the user application proxies this message to another server unchanged and that server also accepts that message but interprets it as two HTTP messages, the second message has reached the second server without having been inspected by the proxy.
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-2021-23339 has been found in com.typesafe.akka:akka-http-core.
Risk of unauthorized operations or information disclosure.
What to do: upgrade com.typesafe.akka:akka-http-core to 10.1.14 or later.
If unsure, ask your IT team or search "com.typesafe.akka:akka-http-core CVE-2021-23339" on the vendor's site.
CVE-2021-23339 (com.typesafe.akka:akka-http-core) — CWE-444
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 10.1.14 — 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 com.typesafe.akka:akka-http-core.
Check the vendor advisory for the affected versions of com.typesafe.akka:akka-http-core.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 10.1.14.
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・依存マニフェストで com.typesafe.akka:akka-http-core を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade com.typesafe.akka:akka-http-core to 10.1.14ステージング環境で 10.1.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web doc.akka.io
- web snyk.io