Denial of Service (DoS) Affecting squid package, versions [,6.5)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Denial of Service (DoS) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-UNMANAGED-SQUID-6249274
- published16 Feb 2024
- disclosed14 Feb 2024
- creditJoshua Rogers
Introduced: 14 Feb 2024
CVE-2024-25617 (opens in a new tab)How to fix?
Upgrade squid to version 6.5 or higher.
Overview
Affected versions of this package are vulnerable to Denial of Service (DoS) due to a Collapse of Data into Unsafe Value bug. This allows a remote client or a remote server to send oversized headers in HTTP messages.
Notes:
1)This can be achieved if the request_header_max_size or reply_header_max_size settings are unchanged from the default in versions prior to 6.5.
All Squid-3.0 up to and including 6.4 without
header_max_sizesettings or with eitherheader_max_sizesetting over 21 KB are vulnerable. Versions with bothheader_max_sizesettings below 21 KB are not vulnerable.All Squid-6.5 and later without
header_max_size configuredor configured with bothheader_max_sizesettings below 64 KB are not vulnerable. Versions configured with eitherheader_max_sizesetting over 64 KB are vulnerable.Run the following command to identify how your Squid has been configured with relevant settings:
squid -k parse 2>&1 | grep header_max_size
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage