Vulnerability Note VU#886006

Squid vulnerable to buffer overflow via an overly long WCCP message

Original Release date: 04 Feb 2005 | Last revised: 08 Feb 2005


The Squid web proxy cache is vulnerable to a buffer overflow when handing overly long web cache communications protocol (WCCP) messages. Such messages could crash the Squid process and produce a denial of service condition.


Squid functions as a web proxy and cache application for number of protocols. It supports WCCP to enable communications between routers and web caches. A recvfrom() call in the WCCP handling routines accepts more data than the buffer size may be able to handle. An attacker may be able to crash the Squid process by sending an overly-long WCCP message.


A remote unauthenticated attacker may be able to crash the Squid process and create a denial of service condition. Sites not using WCCP, which is disabled by default, are not affected.


Apply an update

Administrators should obtain an updated version of Squid from their vendor if WCCP is used.

Team Squid has created a patch for the current release version of Squid, described in Squid Proxy Cache Security Update Advisory SQUID-2005:3.

This flaw has been patched in Squid 2.5.STABLE8-RC4. More details are available in the Squid Bugzilla bug #1217.

Sites not requiring WCCP should disable the 'wccp_router' option in the Squid configuration file. Note that this option is disabled by default.

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
SquidAffected-04 Feb 2005
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A



Thanks to Team Squid for reporting this vulnerability, who in turn credit the FSC Vulnerability Research Team with the discovery of this flaw.

This document was written by Ken MacInnis based primarily on information provided by Team Squid.

Other Information

  • CVE IDs: CAN-2005-0211
  • Date Public: 28 Jan 2005
  • Date First Published: 04 Feb 2005
  • Date Last Updated: 08 Feb 2005
  • Severity Metric: 7.50
  • Document Revision: 20


If you have feedback, comments, or additional information about this vulnerability, please send us email.