Vulnerability in org.http4s:http4s-server_2.13.0-M5 (CVE-2021-39185)
Summary
Vulnerability in org.http4s:http4s-server_2.13.0-M5 (CVE-2021-39185). Confidential information can be exposed externally. Exploitable via CORS. Mitigation: upgrade to 0.21.27 or later.
Original description
The description as published by the source.
Http4s is a minimal, idiomatic Scala interface for HTTP services. In http4s versions 0.21.26 and prior, 0.22.0 through 0.22.2, 0.23.0, 0.23.1, and 1.0.0-M1 through 1.0.0-M24, the default CORS configuration is vulnerable to an origin reflection attack. The middleware is also susceptible to a Null Origin Attack. The problem is fixed in 0.21.27, 0.22.3, 0.23.2, and 1.0.0-M25. The original CORS implementation and CORSConfig are deprecated. See the GitHub GHSA for more information, including code examples and workarounds.
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-39185 has been found in org.http4s:http4s-server_2.13.0-M5.
Attackers can target a specific entry point like CORS over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade org.http4s:http4s-server_2.13.0-M5 to 0.21.27 or later.
If unsure, ask your IT team or search "org.http4s:http4s-server_2.13.0-M5 CVE-2021-39185" on the vendor's site.
CVE-2021-39185 (org.http4s:http4s-server_2.13.0-M5) — CWE-346
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: CORS / CORSConfig
Patched: 0.21.27 — 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-346) exists in org.http4s:http4s-server_2.13.0-M5. Attackers reach the vulnerable code path via CORS without authentication.
Check the vendor advisory for the affected versions of org.http4s:http4s-server_2.13.0-M5. Attack surface: CORS / CORSConfig.
Severity: ?. Confidential information can be exposed externally.
Update to 0.21.27.
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・依存マニフェストで org.http4s:http4s-server_2.13.0-M5 を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.http4s:http4s-server_2.13.0-M5 to 0.21.27ステージング環境で 0.21.27 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com