Vulnerability record · CVE-2024-25111 · published 6 March 2024
CVE-2024-25111: Squid HTTP chunked decoder recursion denial of service
Squid Cache · Squid
Squid versions 3.5.27 through 6.7 contain an uncontrolled recursion bug in the HTTP chunked decoder. A remote attacker can send a crafted chunked-encoded HTTP message that drives deep recursion and causes a denial of service. The flaw is fixed in Squid 6.8, and no workaround exists.
Description
Squid is a web proxy cache. Starting in version 3.5.27 and prior to version 6.8, Squid may be vulnerable to a Denial of Service attack against HTTP Chunked decoder due to an uncontrolled recursion bug. This problem allows a remote attacker to cause Denial of Service when sending a crafted, chunked, encoded HTTP Message. This bug is fixed in Squid version 6.8. In addition, patches addressing this problem for the stable releases can be found in Squid's patch archives. There is no workaround for this issue.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Automated analysis
high priorityRemote, unauthenticated denial of service with a high EPSS score and no workaround, though it only affects availability.
What it is
Squid versions 3.5.27 through 6.7 contain an uncontrolled recursion bug in the HTTP chunked decoder. A remote attacker can send a crafted chunked-encoded HTTP message that drives deep recursion and causes a denial of service. The flaw is fixed in Squid 6.8, and no workaround exists.
Impact
An attacker can crash or exhaust the Squid proxy process, disrupting web access for all users relying on it. Only availability is affected; there is no confidentiality or integrity impact.
Attack surface
Reachable over the network by sending a crafted chunked HTTP message to the Squid proxy, per the CVSS vector AV:N/AC:L/PR:N/UI:N. No authentication or user interaction is required.
Exploitation
Not listed in CISA KEV and no public exploit references are tagged, but EPSS is high at roughly 0.65 (99th percentile), indicating elevated likelihood of exploitation activity.
What to do
- Upgrade Squid to version 6.8 or later.
- Apply the vendor patch SQUID-2024_1 for stable release branches that cannot move to 6.8.
- Update distribution packages (Fedora, Debian LTS) and NetApp BlueXP components that bundle Squid.
- Restrict or monitor direct access to Squid proxy ports from untrusted networks.
- Plan for service interruption since no configuration workaround exists.
Detection
- Monitor Squid logs for crashes, restarts, or abnormal termination of the proxy process.
- Alert on high CPU or memory spikes in Squid correlated with chunked transfer-encoded requests.
- Inspect proxy access logs for malformed or unusually deep chunked HTTP messages from single sources.
- Track repeated connection attempts to the proxy port that precede service unavailability.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Affected products
3 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
Track CVE-2024-25111 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2024-25111), CISA KEV, FIRST EPSS (scores of 2026-09-27). This page is refreshed as NVD updates the record.