CVE Explore

XXE in Http4k

CVE-2024-55875

CVSS v3
9.8 Critical
Public exploits
1 repository
EPSS
0.019 · 80.0th percentile
Published
2024-12-12

What to do

Fixed in
6.50.0.0, 5.41.0.0
Affected
1 affected product

http4k is a functional toolkit for Kotlin HTTP applications. Prior to version 6.50.0.0, there is a potential XXE (XML External Entity Injection) vulnerability when http4k handling malicious XML contents within requests, which might allow attackers to read local sensitive information on server, trigger Server-side Request Forgery and even execute code under some circumstances. The original fix shipped in v5.41.0.0 / v4.50.0.0 closed the documented external-entity attack class (SSRF, local-file disclosure, code execution) by setting `ACCESS_EXTERNAL_DTD=""`, `ACCESS_EXTERNAL_SCHEMA=""`, and `isExpandEntityReferences=false` on the default `DocumentBuilderFactory`. A residual gap remained: the parser still accepted documents containing `<!DOCTYPE>` declarations even though external entity resolution was blocked. This left open billion-laughs-style internal entity expansion DoS attacks against any application using `Body.xml()` or `Document.asXmlDocument()` on untrusted XML. v6.50.0.0 closes this residual by adding `disallow-doctype-decl=true` and `FEATURE_SECURE_PROCESSING=true` to `defaultXmlParsingConfig`. Any document containing a `<!DOCTYPE>` is now rejected at parse time.

Vulnerability class: Information Disclosure

Published · last modified .

CVSS v3 metric

CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Attack Vector
Network AV:N
Attack Complexity
Low AC:L
Privileges Required
None PR:N
User Interaction
None UI:N
Scope
Unchanged S:U
Confidentiality
High C:H
Integrity
High I:H
Availability
High A:H

EPSS exploit prediction

EPSS 0.019, 80.0th percentile (last changed ); unchanged over 30 days. About EPSS.

Affected products

  • Http4k — versions < 6.50.0.0, < 5.41.0.0

Weakness classification (CWE)

Public exploits and proof-of-concept code

1 public repository with exploit or proof-of-concept code for this CVE:

Also mentioned in 1 other repository (nomi-sec/PoC-in-GitHub). These reference the CVE in a list, notes or a scanner and are not exploit code for it.

References