CVE-2024-31309

CRITICALNVD 7.59.0
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 95% probability of exploitation within the next 30 days (top 0.2% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 95%
CISA-KEV: Not listedEPSS PROB: 95%CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

HTTP/2 CONTINUATION DoS attack can cause Apache Traffic Server to consume more resources on the server.  Version from 8.0.0 through 8.1.9, from 9.0.0 through 9.2.3 are affected.

Users can set a new setting (proxy.config.http2.max_continuation_frames_per_minute) to limit the number of CONTINUATION frames per minute.  ATS does have a fixed amount of memory a request can use and ATS adheres to these limits in previous releases. Users are recommended to upgrade to versions 8.1.10 or 9.2.4 which fixes the issue.

CVSS v3
7.5
EG Score
9.0(high)
EG Risk
93(Track)
EG Risk 93/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation95% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
95%
EPSS %ILE
100%
KEV
Not listed

Published

April 10, 2024

Last Modified

November 4, 2025

References (15)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-08 04:19 UTCOSV refresh
  2. 2026-08-07 16:25 UTCEPSS rescore
  3. 2026-08-06 13:45 UTCEPSS rescore
  4. 2026-08-04 15:08 UTCEPSS rescore
  5. 2026-08-04 10:36 UTCEPSS rescore
  6. 2026-08-03 10:34 UTCEPSS rescore
  7. 2026-08-02 02:25 UTCEPSS rescore
  8. 2026-08-02 02:25 UTCEPSS rescore
  9. 2026-07-30 16:26 UTCEPSS rescore
  10. 2026-07-30 16:26 UTCEPSS rescore
  11. 2026-07-30 01:29 UTCEPSS rescore
  12. 2026-07-28 15:34 UTCEPSS rescore
  13. 2026-07-24 14:16 UTCEPSS rescore
  14. 2026-07-23 02:36 UTCEG score recompute
  15. 2026-07-22 21:22 UTCEG score recompute 1.50
  16. 2026-07-22 21:21 UTCGHSA enrichment
  17. 2026-07-22 14:07 UTCEPSS rescore
  18. 2026-07-21 15:23 UTCEPSS rescore
  19. 2026-07-20 17:06 UTCEPSS rescore
  20. 2026-07-14 14:25 UTCOSV refresh
  21. 2026-07-13 22:28 UTCEPSS rescore
  22. 2026-07-13 06:11 UTCEPSS rescore
  23. 2026-07-01 15:05 UTCEPSS rescore
  24. 2026-06-26 15:07 UTCOSV refresh
  25. 2026-06-24 14:04 UTCEPSS rescore
Show 48 more
  1. 2026-06-24 14:04 UTCEPSS rescore
  2. 2026-06-23 21:32 UTCEPSS rescore
  3. 2026-06-23 21:32 UTCEPSS rescore
  4. 2026-06-17 17:52 UTCEPSS rescore
  5. 2026-06-17 17:52 UTCEPSS rescore
  6. 2026-06-15 17:47 UTCEPSS rescore
  7. 2026-06-14 23:16 UTCEPSS rescore
  8. 2026-06-13 22:59 UTCEPSS rescore
  9. 2026-06-13 22:59 UTCEPSS rescore
  10. 2026-06-12 23:11 UTCEPSS rescore
  11. 2026-06-12 23:11 UTCEPSS rescore
  12. 2026-06-11 13:59 UTCEPSS rescore
  13. 2026-06-10 22:17 UTCEPSS rescore
  14. 2026-06-10 13:21 UTCEPSS rescore
  15. 2026-06-10 13:21 UTCEPSS rescore
  16. 2026-06-08 21:42 UTCOSV refresh
  17. 2026-06-08 14:16 UTCEPSS rescore
  18. 2026-06-07 15:24 UTCEPSS rescore
  19. 2026-06-07 15:24 UTCEPSS rescore
  20. 2026-06-05 22:46 UTCEPSS rescore
  21. 2026-06-05 22:46 UTCEPSS rescore
  22. 2026-06-05 06:09 UTCEPSS rescore
  23. 2026-06-05 06:09 UTCEPSS rescore
  24. 2026-06-04 13:11 UTCEPSS rescore
  25. 2026-06-04 13:11 UTCEPSS rescore
  26. 2026-06-04 13:11 UTCEPSS rescore
  27. 2026-06-02 20:12 UTCEPSS rescore
  28. 2026-06-02 20:12 UTCEPSS rescore
  29. 2026-06-01 13:51 UTCEPSS rescore
  30. 2026-06-01 13:51 UTCEPSS rescore
  31. 2026-06-01 13:51 UTCEPSS rescore
  32. 2026-05-31 22:30 UTCEPSS rescore
  33. 2026-05-31 22:30 UTCEPSS rescore
  34. 2026-05-31 00:15 UTCEPSS rescore
  35. 2026-05-31 00:15 UTCEPSS rescore
  36. 2026-05-29 13:43 UTCEPSS rescore
  37. 2026-05-29 13:43 UTCEPSS rescore
  38. 2026-05-28 13:44 UTCEPSS rescore
  39. 2026-05-28 13:44 UTCEPSS rescore
  40. 2026-05-28 13:44 UTCEPSS rescore
  41. 2026-05-27 13:40 UTCEPSS rescore
  42. 2026-05-27 13:40 UTCEPSS rescore
  43. 2026-05-26 13:43 UTCEPSS rescore
  44. 2026-05-26 13:43 UTCEPSS rescore
  45. 2026-05-26 07:18 UTCEPSS rescore
  46. 2026-05-26 07:18 UTCEPSS rescore
  47. 2026-05-24 04:46 UTCEG score recompute
  48. 2026-05-24 04:46 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2024-31309?
CVE-2024-31309 is a critical vulnerability published on April 10, 2024. HTTP/2 CONTINUATION DoS attack can cause Apache Traffic Server to consume more resources on the server. Version from 8.0.0 through 8.1.9, from 9.0.0 through 9.2.3 are affected. Users can set a new setting (proxy.config.http2.maxcontinuationframesperminute) to limit the number of CONTINUATION frames…
When was CVE-2024-31309 disclosed?
CVE-2024-31309 was first published in the National Vulnerability Database on April 10, 2024, with the most recent update on November 4, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-31309 actively exploited?
CVE-2024-31309 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95% probability of exploitation in the next 30 days, which ranks it in the top 0.2% of all scored CVEs.
What is the CVSS score of CVE-2024-31309?
CVE-2024-31309 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2024-31309?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-31309, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-31309

Explore →

Is Your Infrastructure Affected by CVE-2024-31309?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.