Vulnerability in org.http4s:http4s-server_2.12 (CVE-2020-5280)
Summary
Vulnerability in org.http4s:http4s-server_2.12 (CVE-2020-5280). Confidential information can be exposed externally. Exploitable via FileService. Mitigation: upgrade to 0.21.2 or later.
Original description
The description as published by the source.
Impact
This vulnerability applies to all users of:
org.http4s.server.staticcontent.FileServiceorg.http4s.server.staticcontent.ResourceServiceorg.http4s.server.staticcontent.WebjarService
Path escaping
URI normalization is applied incorrectly. Requests whose path info contain ../ or // can expose resources outside of the configured location. Specifically:
FileServicemay expose any file on the local file system.ResourceServicemay expose any resource on the class path.
Prefix matching
When the service is configured with a non-empty pathPrefix that doesn't end in a slash, any directories whose names are a prefix of systemPath (from FileService) or pathPrefix (from ResourceService) are exposed. For example, if pathPrefix is /foo and systemPath is /bar, a request to /foobaz/quux.txt exposes file /barbaz/quux.txt, when only files beneath /bar should be available.
URI decoding
URI segments are not decoded before resource resolution. This causes resources with reserved characters in their name to incorrectly return a 404. It also may incorrectly expose the rare resource whose name is URI encoded. This applies to FileService, ResourceService, and WebjarService.
Patches
In all three services, paths with an empty segment, a . segment, or a .. segment are now rejected with a 400 Bad Request response. This fixes exposure outside the configured root. Many clients already eliminate dot s…
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-5280 has been found in org.http4s:http4s-server_2.12.
Attackers can target a specific entry point like FileService over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade org.http4s:http4s-server_2.12 to 0.21.2 or later.
If unsure, ask your IT team or search "org.http4s:http4s-server_2.12 CVE-2020-5280" on the vendor's site.
CVE-2020-5280 (org.http4s:http4s-server_2.12) — CWE-23
Attack vector: remote (network-reachable)
Attack surface: FileService / ResourceService / pathPrefix / systemPath
Patched: 0.21.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-23) exists in org.http4s:http4s-server_2.12. Attackers reach the vulnerable code path via FileService.
Check the vendor advisory for the affected versions of org.http4s:http4s-server_2.12. Attack surface: FileService / ResourceService / pathPrefix / systemPath.
Severity: ?. Confidential information can be exposed externally.
Update to 0.21.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・依存マニフェストで org.http4s:http4s-server_2.12 を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.http4s:http4s-server_2.12 to 0.21.2ステージング環境で 0.21.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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 github.com
- web github.com