VYPR
Unrated severityNVD Advisory· Published Feb 14, 2024· Updated Feb 13, 2025

Denial of Service in HTTP Header parser in squid proxy

CVE-2024-25617

Description

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

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Affected products

23

Patches

Vulnerability mechanics

Root cause

"A Collapse of Data into Unsafe Value bug allows for Denial of Service when handling oversized HTTP headers."

Attack vector

A remote client or server can trigger a Denial of Service by sending oversized headers in HTTP messages. This is particularly effective if the `request_header_max_size` or `reply_header_max_size` settings are not changed from their default values in Squid versions prior to 6.5. In version 6.5 and later, the default settings are safe, but the application will still emit a warning if an administrator configures these parameters to unsafe values.

Affected code

The vulnerability lies within the HTTP header parsing logic in Squid. Specifically, the configuration parameters `request_header_max_size` and `reply_header_max_size` are involved. The patch modifies the `configDoConfigure` function to include checks and warnings for these header size limits [ref_id=1].

What the fix does

The patch introduces checks to warn administrators if `request_header_max_size` or `reply_header_max_size` are set to values that exceed a calculated safe limit, which is approximately one-third of the maximum String size. This limit is intended to mitigate the risk of Denial of Service attacks related to oversized headers. While the warning is emitted, the application does not prevent the configuration of these unsafe values at this time [ref_id=1].

Preconditions

  • configIn versions prior to 6.5, the `request_header_max_size` or `reply_header_max_size` settings must be at their default values for the vulnerability to be easily exploitable. In 6.5 and later, the defaults are safe, but administrators can still configure unsafe values.

Generated on Jun 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

3

News mentions

0

No linked articles in our index yet.