CVE-2024-25617

MEDIUMNVD 5.39.0▲
EchelonGraph scoreHIGH confidence

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

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
5.3
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 89%
CISA-KEV: Not listedEPSS: 89%CVSS: 5.3Exploit: NoneExposed: 0

A fix is available — apply it.

Squid is an open source caching proxy for the Web supporting HTTP, HTTPS, FTP, and more. Due to a Collapse of Data into Unsafe Value bug ,Squid may be vulnerable to a Denial of Service attack against HTTP header parsing. This problem allows a remote client or a remote server to perform Denial of Service when sending oversized headers in HTTP messages. In versions of Squid prior to 6.5 this can be achieved if the request_header_max_size or reply_header_max_size settings are unchanged from the default. In Squid version 6.5 and later, the default setting of these parameters is safe. Squid will emit a critical warning in cache.log if the administrator is setting these parameters to unsafe values. Squid will not at this time prevent these settings from being changed to unsafe values. Users are advised to upgrade to version 6.5. There are no known workarounds for this vulnerability. This issue is also tracked as SQUID-2024:2

CVSS v3
5.3
EG Score
9.0(high)
EG Risk
91(Track)
EG Risk 91/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%
Exploitation89% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.8%
KEV
Not listed

Published

February 14, 2024

Last Modified

June 25, 2025

References (6)

Vendor Advisories for CVE-2024-25617(9)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntusquidclient (5.7-0ubuntu0.22.04.4) @ jammy2026-07-22ubuntu
ubuntusquidclient (3.5.12-1ubuntu7.16+esm3) @ xenial2026-07-22ubuntu
redhatsquid:4-8020020240313150557.4cda2c842024-05-09redhat
redhatsquid-7:5.2-1.el9_0.62024-04-16redhat
redhatsquid:4-8040020240312224211.522a0ee42024-04-16redhat
redhatsquid-7:3.5.20-17.el7_9.102024-04-11redhat
redhatsquid-7:5.5-6.el9_3.82024-03-19redhat
redhatsquid:4-8090020240314114525.a75119d52024-03-19redhat
redhatsquid-7:5.5-5.el9_2.52024-03-06redhat
redhatsquid:4-8060020240227214219.ad008a3a2024-03-04redhat
redhatsquid:4-8080020240227184832.63b345852024-03-01redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 25× 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-07-23 02:34 UTCEG score recompute
  2. 2026-07-22 21:22 UTCEG score recompute▲ 3.70
  3. 2026-07-22 21:22 UTCVendor advisory
  4. 2026-07-22 14:07 UTCEPSS rescore
  5. 2026-07-19 02:28 UTCEPSS rescore
  6. 2026-07-19 02:28 UTCEPSS rescore
  7. 2026-07-15 16:56 UTCEPSS rescore
  8. 2026-07-15 16:56 UTCEPSS rescore
  9. 2026-07-14 19:40 UTCOSV refresh
  10. 2026-07-13 06:11 UTCEPSS rescore
  11. 2026-07-13 06:11 UTCEPSS rescore
  12. 2026-07-06 02:22 UTCEPSS rescore
  13. 2026-07-06 02:22 UTCEPSS rescore
  14. 2026-07-01 15:05 UTCEPSS rescore
  15. 2026-06-30 23:21 UTCEPSS rescore
  16. 2026-06-30 23:21 UTCEPSS rescore
  17. 2026-06-28 04:55 UTCEPSS rescore
  18. 2026-06-28 04:55 UTCEPSS rescore
  19. 2026-06-27 03:07 UTCEPSS rescore
  20. 2026-06-27 03:07 UTCEPSS rescore
  21. 2026-06-26 20:37 UTCOSV refresh
  22. 2026-06-24 14:04 UTCEPSS rescore
  23. 2026-06-24 14:04 UTCEPSS rescore
  24. 2026-06-23 21:32 UTCEPSS rescore
  25. 2026-06-23 21:32 UTCEPSS rescore
Show 48 more
  1. 2026-06-16 17:51 UTCEPSS rescore
  2. 2026-06-16 17:51 UTCEPSS rescore
  3. 2026-06-15 17:47 UTCEPSS rescore
  4. 2026-06-14 23:16 UTCEPSS rescore
  5. 2026-06-13 22:59 UTCEPSS rescore
  6. 2026-06-13 22:59 UTCEPSS rescore
  7. 2026-06-12 23:11 UTCEPSS rescore
  8. 2026-06-11 13:59 UTCEPSS rescore
  9. 2026-06-11 13:59 UTCEPSS rescore
  10. 2026-06-10 22:17 UTCEPSS rescore
  11. 2026-06-10 13:21 UTCEPSS rescore
  12. 2026-06-10 13:21 UTCEPSS rescore
  13. 2026-06-09 06:30 UTCOSV refresh
  14. 2026-06-08 14:16 UTCEPSS rescore
  15. 2026-06-08 14:16 UTCEPSS rescore
  16. 2026-06-07 15:24 UTCEPSS rescore
  17. 2026-06-07 15:24 UTCEPSS rescore
  18. 2026-06-06 13:46 UTCEPSS rescore
  19. 2026-06-06 13:46 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 08:29 UTCEG score recompute
  48. 2026-05-24 08:29 UTCVendor advisory

Frequently asked(5)

What is CVE-2024-25617?
CVE-2024-25617 is a medium vulnerability published on February 14, 2024. Squid is an open source caching proxy for the Web supporting HTTP, HTTPS, FTP, and more. Due to a Collapse of Data into Unsafe Value bug ,Squid may be vulnerable to a Denial of Service attack against HTTP header parsing. This problem allows a remote client or a remote server to perform Denial of…
When was CVE-2024-25617 disclosed?
CVE-2024-25617 was first published in the National Vulnerability Database on February 14, 2024, with the most recent update on June 25, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-25617 actively exploited?
CVE-2024-25617 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-25617?
CVE-2024-25617 has a CVSS v3 base score of 5.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2024-25617?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-25617, 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-25617

Explore →

Is Your Infrastructure Affected by CVE-2024-25617?

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

Start Free Scan →Browse All CVEs