CVE-2024-25617: Denial of Service in HTTP Header parser in squid proxy

Published Feb 14, 2024
·
Updated

Last updated 13 January 2025

Other sources

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 requestheadermaxsize or replyheadermaxsize 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

Launchpad

Affected Software

5 affected componentsFixes available
redhat/squid<6.5
6.5
debian/squid
4.13-10+deb11u35.7-2+deb12u26.13-1
Squid-Cache Squid<6.5
NetApp Bluexp
Squid-Cache Squid>=3.0<6.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/squid to a version that resolves this vulnerability.

    Fixed in 6.5
  2. Upgrade

    Upgrade debian/squid to a version that resolves this vulnerability.

    Fixed in 4.13-10+deb11u3Fixed in 5.7-2+deb12u2Fixed in 6.13-1
  3. Upgrade

    Upgrade squid-cache/squid to a version that resolves this vulnerability.

    Fixed in 6.5
  4. Configuration

    For Squid versions prior to 6.5, ensure request_header_max_size and reply_header_max_size are left unchanged from their default safe values; do not set them to unsafe values (Squid logs a critical warning in cache.log when set to unsafe values).

    Squid proxy request_header_max_size or reply_header_max_size = unchanged from the default (safe)

Event History

Feb 14, 2024
CVE Published
via MITRE·08:55 PM
Data Sourced
via MITRE·08:55 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 10, 2024
Data Sourced
via Launchpad·05:40 PM
Description
Jan 17, 2025
Data Sourced
via Ubuntu·05:23 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-25617?

CVE-2024-25617 is considered a high severity vulnerability due to the potential for Denial of Service attacks.

2

How do I fix CVE-2024-25617?

To fix CVE-2024-25617, upgrade Squid to version 6.5 or any patched version specific to Debian as detailed in the security advisories.

3

Which versions of Squid are affected by CVE-2024-25617?

CVE-2024-25617 affects Squid versions prior to 6.5 and specific older versions of Squid on Debian and Red Hat.

4

Is there a workaround for CVE-2024-25617?

Currently, there is no official workaround for CVE-2024-25617, and it's advised to upgrade to a secured version.

5

What kind of attack can CVE-2024-25617 lead to?

CVE-2024-25617 can lead to Denial of Service attacks that disrupt HTTP header parsing in Squid.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203