| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Squid Proxy up to 2.5.STABLE7 and classified as problematic. Affected is an unknown function of the component Reply Header Handler. This manipulation as part of Large Header causes an unknown weakness. This vulnerability is registered as CVE-2005-0241. Remote exploitation of the attack is possible. No exploit is available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability has been found in Squid Proxy up to 2.5.STABLE7 (Firewall Software) and classified as problematic. Affected by this vulnerability is an unknown part of the component Reply Header Handler. The manipulation as part of a Large Header leads to a unknown weakness. As an impact it is known to affect integrity. The summary by CVE is:
The httpProcessReplyHeader function in http.c for Squid 2.5-STABLE7 and earlier does not properly set the debug context when it is handling "oversized" HTTP reply headers, which might allow remote attackers to poison the cache or bypass access controls based on header size.
The bug was discovered 02/04/2005. The weakness was published 02/03/2005 with Squid Team (Website). The advisory is shared at squid-cache.org. This vulnerability is known as CVE-2005-0241 since 02/08/2005. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.
It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 19108 (FreeBSD : squid -- correct handling of oversized HTTP reply headers (bfda39de-7467-11d9-9e1e-c296ac722cb3)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks and running in the context l.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at squid-cache.org. A possible mitigation has been published 5 days after the disclosure of the vulnerability. Attack attempts may be identified with Snort ID 15580. In this case the pattern Content-Length|3A| 3|0D 0A|Server|3A| AAAAAA is used for detection. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 9118.
The vulnerability is also documented in the databases at X-Force (19060), Tenable (19108), SecurityFocus (BID 12412†), OSVDB (13345†) and Secunia (SA14091†). Similar entries are available at VDB-23916 and VDB-23915. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: http://www.squid-cache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: UnknownCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 19108
Nessus Name: FreeBSD : squid -- correct handling of oversized HTTP reply headers (bfda39de-7467-11d9-9e1e-c296ac722cb3)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍
OpenVAS ID: 52196
OpenVAS Name: FreeBSD Ports: squid
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: squid-cache.org
Snort ID: 15580
Snort Message: SPECIFIC-THREATS Squid oversized reply header handling exploit attempt
Snort Pattern: 🔍
TippingPoint: 🔍
SourceFire IPS: 🔍
ISS Proventia IPS: 🔍
PaloAlto IPS: 🔍
Timeline
01/25/2005 🔍02/01/2005 🔍
02/01/2005 🔍
02/01/2005 🔍
02/03/2005 🔍
02/03/2005 🔍
02/04/2005 🔍
02/08/2005 🔍
02/08/2005 🔍
02/17/2005 🔍
05/02/2005 🔍
07/13/2005 🔍
12/16/2024 🔍
Sources
Vendor: squid-cache.orgAdvisory: squid-cache.org
Researcher: http://www.squid-cache.org
Organization: Squid Team
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2005-0241 (🔍)
GCVE (CVE): GCVE-0-2005-0241
GCVE (VulDB): GCVE-100-1165
OVAL: 🔍
CERT: 🔍
X-Force: 19060 - Squid Web Proxy Cache HTTP header cache poisoning, Medium Risk
SecurityFocus: 12412 - Squid Proxy Oversize HTTP Headers Unspecified Remote Vulnerability
Secunia: 14091 - Squid Oversized Reply Header Handling Security Issue, Less Critical
OSVDB: 13345 - Squid Oversized Reply Header Handling Security Issue
Vulnerability Center: 7105 - Squid 2.5.STABLE7 and Prior Cache Poisoning via Oversized HTTP Reply Headers, Medium
See also: 🔍
Entry
Created: 02/03/2005 18:54Updated: 12/16/2024 11:09
Changes: 02/03/2005 18:54 (103), 07/01/2019 09:11 (2), 12/16/2024 11:09 (18)
Complete: 🔍
Cache ID: 216:D6F:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.