Squid Proxy up to 2.5.stable6 wccp.c recvfrom length memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.0$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in Squid Proxy up to 2.5.stable6. This impacts the function recvfrom of the file wccp.c. The manipulation of the argument length leads to memory corruption. This vulnerability is documented as CVE-2005-0211. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Squid Proxy up to 2.5.stable6 (Firewall Software) and classified as critical. This issue affects the function recvfrom of the file wccp.c. The manipulation of the argument length with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Buffer overflow in wccp.c in Squid 2.5 before 2.5.STABLE7 allows remote attackers to cause a denial of service and possibly execute arbitrary code via a long WCCP packet, which is processed by a recvfrom function call that uses an incorrect length parameter.

The bug was discovered 01/28/2005. The weakness was released 01/18/2005 by ERNE as confirmed advisory (CERT.org). The advisory is shared at kb.cert.org. The identification of this vulnerability is CVE-2005-0211 since 02/01/2005. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 18872 (FreeBSD : squid -- buffer overflow in WCCP recvfrom() call (23fb5a04-722b-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.

Upgrading to version 2.5 eliminates this vulnerability. A possible mitigation has been published 2 weeks after the disclosure of the vulnerability. Attack attempts may be identified with Snort ID 12222. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 9122.

The vulnerability is also documented in the databases at X-Force (19142), Tenable (18872), SecurityFocus (BID 12432†), OSVDB (13319†) and Secunia (SA14076†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.0

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 18872
Nessus Name: FreeBSD : squid -- buffer overflow in WCCP recvfrom() call (23fb5a04-722b-11d9-9e1e-c296ac722cb3)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 53497
OpenVAS Name: Debian Security Advisory DSA 667-1 (postgresql)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Proxy 2.5

Snort ID: 12222
TippingPoint: 🔍

McAfee IPS: 🔍
McAfee IPS Version: 🔍

ISS Proventia IPS: 🔍
PaloAlto IPS: 🔍
Fortigate IPS: 🔍

Timelineinfo

01/18/2005 🔍
01/28/2005 +9 days 🔍
01/28/2005 +0 days 🔍
01/28/2005 +0 days 🔍
01/31/2005 +3 days 🔍
01/31/2005 +0 days 🔍
02/01/2005 +0 days 🔍
02/02/2005 +1 days 🔍
02/17/2005 +15 days 🔍
05/02/2005 +74 days 🔍
07/13/2005 +72 days 🔍
03/10/2015 +3527 days 🔍
01/03/2025 +3587 days 🔍

Sourcesinfo

Vendor: squid-cache.org

Advisory: kb.cert.org
Researcher: ERNE
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2005-0211 (🔍)
GCVE (CVE): GCVE-0-2005-0211
GCVE (VulDB): GCVE-100-24341

OVAL: 🔍

CERT: 🔍
X-Force: 19142
SecurityFocus: 12432 - Squid Proxy WCCP recvfrom() Buffer Overflow Vulnerability
Secunia: 14076
OSVDB: 13319 - Squid WCCP recvfrom() Function Overflow
SecurityTracker: 1013045
Vulnerability Center: 7104 - DoS in Squid 2.5.STABLE7 and Prior via Long WCCP Packet, High

Entryinfo

Created: 03/10/2015 23:05
Updated: 01/03/2025 18:57
Changes: 03/10/2015 23:05 (88), 05/30/2019 10:33 (9), 01/03/2025 18:57 (17)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!