Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Withdrawn — this advisory has been retracted
📦 Debian:13

CVE-2024-5971

HIGH

Undertow Denial of Service vulnerability

Also known asGHSA-xpp6-8r3j-ww43
Published
Jul 8, 2024
Updated
Jan 9, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
2.7%probability of exploitation in next 30 days
Lower Risk84th percentile-0.98%
0.00%1.56%3.12%4.68%0.4%2.7%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected
📦undertow

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Debian:13 packages — download data is not available via public APIs for these ecosystems.

Description

A vulnerability was found in Undertow, where the chunked response hangs after the body was flushed. The response headers and body were sent but the client would continue waiting as Undertow does not send the expected 0\r\n termination of the chunked response. This results in uncontrolled resource consumption, leaving the server side to a denial of service attack. This happens only with Java 17 TLSv1.3 scenarios.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦Debian:13undertowall versions2.3.18-1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for undertow. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update undertow to 2.3.18-1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-5971 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2024-5971 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-5971. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A vulnerability was found in Undertow, where the chunked response hangs after the body was flushed. The response headers and body were sent but the client would continue waiting as Undertow does not send the expected 0\r\n termination of the chunked response. This results in uncontrolled resource consumption, leaving the server side to a denial of service attack. This happens only with Java 17 TLSv1.3 scenarios.
O3 Security · Impact-Aware SCA

Is CVE-2024-5971 in your dependencies?

O3 detects CVE-2024-5971 across Debian:13 dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.