← Back
CVE-2024-55875
critical
CVSS 9.8
Information Disclosure in org.http4k:http4k-format-xml (CVE-2024-55875)
Summary
vulnerability in org.http4k:http4k-format-xml (CVE-2024-55875). Successful exploitation can lead to full system takeover. Exploitable via ``DocumentBuilderFactory``. Mitigation: upgrade to `6.50.0.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-55875** has been found in org.http4k:http4k-format-xml.
Attackers can target a specific entry point like ``DocumentBuilderFactory`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade org.http4k:http4k-format-xml to **6.50.0.0** or later.
If unsure, ask your IT team or search "org.http4k:http4k-format-xml CVE-2024-55875" on the vendor's site.
CVE-2024-55875 (org.http4k:http4k-format-xml) — CWE-200 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `DocumentBuilderFactory` / `defaultXmlParsingConfig` / `c0cfaf5d63`
Patched: `6.50.0.0` — 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.
❓ What is the problem
**information disclosure** (CWE-200) exists in org.http4k:http4k-format-xml. Attackers reach the vulnerable code path via ``DocumentBuilderFactory`` without authentication.
📍 Affected scope
org.http4k:http4k-format-xml — . Attack surface: `DocumentBuilderFactory` / `defaultXmlParsingConfig` / `c0cfaf5d63`.
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **6.50.0.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.http4k:http4k-format-xml' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.http4k:http4k-format-xml' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.http4k:http4k-format-xml` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade org.http4k:http4k-format-xml to 6.50.0.0ステージング環境で 6.50.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.http4k:http4k-format-xml
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.50.0.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-55875
- package https://github.com/http4k/http4k
- web https://github.com/http4k/http4k/security/advisories/GHSA-7mj5-hjjj-8rgw
- web https://github.com/http4k/http4k/commit/35297adc6d6aca4951d50d8cdf17ff87a8b19fbc
- web https://github.com/http4k/http4k/blob/25696dff2d90206cc1da42f42a1a8dbcdbcdf18c/core/format/xml/src/main/kotlin/org/http4k/format/Xml.kt#L42-L46
- web https://github.com/advisories/GHSA-7mj5-hjjj-8rgw