The WCCP message parsing code in Squid 2.5.STABLE7 and earlier allows remote attackers to cause a denial of service (crash) via malformed WCCP messages with source addresses that are spoofed to reference Squid's home router and invalid WCCP_I_SEE_YOU cache numbers.

infamous41md discovered several Denial of Service vulnerabilities in squid.

A malicious Gopher server could crash squid by sending a line bigger than 4096 bytes. (CAN-2005-0094)

If squid is configured to send WCPP (Web Cache Communication Protocol) messages to a 'home router', an attacker who was able to send UDP packets with a forged source address of this router could crash the

erver with a specially crafted WCPP message. (CAN-2005-0095)

Previous versions of squid have a memory leak which gradually cause memory exhaustion and eventual termination. (CAN-2005-0096)

A remote attacker could crash the server by sending a specially crafted NTLM type 3 packet. (CAN-2005-0097).

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The squid patches page notes :

WCCP_I_SEE_YOU messages contain a 'number of caches' field which should be between 1 and 32. Values outside that range may crash Squid if WCCP is enabled, and if an attacker can spoof UDP packets with the WCCP router's IP address.

The remote Redhat Enterprise Linux 4 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2005:060 advisory.

    Squid is a full-featured Web proxy cache.

    A buffer overflow flaw was found in the Gopher relay parser. This bug     could allow a remote Gopher server to crash the Squid proxy that reads data     from it. Although Gopher servers are now quite rare, a malicious webpage     (for example) could redirect or contain a frame pointing to an attacker's     malicious gopher server. The Common Vulnerabilities and Exposures project     (cve.mitre.org) has assigned the name CAN-2005-0094 to this issue.

    An integer overflow flaw was found in the WCCP message parser. It is     possible to crash the Squid server if an attacker is able to send a     malformed WCCP message with a spoofed source address matching Squid's     home router. The Common Vulnerabilities and Exposures project     (cve.mitre.org) has assigned the name CAN-2005-0095 to this issue.

    A memory leak was found in the NTLM fakeauth_auth helper. It is possible     that an attacker could place the Squid server under high load, causing the     NTML fakeauth_auth helper to consume a large amount of memory, resulting in     a denial of service. The Common Vulnerabilities and Exposures project     (cve.mitre.org) has assigned the name CAN-2005-0096 to this issue.

    A NULL pointer de-reference bug was found in the NTLM fakeauth_auth helper.
    It is possible for an attacker to send a malformed NTLM type 3 message,     causing the Squid server to crash. The Common Vulnerabilities and     Exposures project (cve.mitre.org) has assigned the name CAN-2005-0097 to     this issue.

    A username validation bug was found in squid_ldap_auth. It is possible for     a username to be padded with spaces, which could allow a user to bypass     explicit access control rules or confuse accounting. The Common     Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name     CAN-2005-0173 to this issue.

    The way Squid handles HTTP responses was found to need strengthening. It is     possible that a malicious Web server could send a series of HTTP responses     in such a way that the Squid cache could be poisoned, presenting users with     incorrect webpages. The Common Vulnerabilities and Exposures project     (cve.mitre.org) has assigned the names CAN-2005-0174 and CAN-2005-0175 to     these issues.

    A bug was found in the way Squid handled oversized HTTP response headers.
    It is possible that a malicious Web server could send a specially crafted     HTTP header which could cause the Squid cache to be poisoned, presenting     users with incorrect webpages. The Common Vulnerabilities and Exposures     project (cve.mitre.org) has assigned the name CAN-2005-0241 to this issue.

    A buffer overflow bug was found in the WCCP message parser. It is possible     that an attacker could send a malformed WCCP message which could crash the     Squid server or execute arbitrary code. The Common Vulnerabilities and     Exposures project (cve.mitre.org) has assigned the name CAN-2005-0211     to this issue.

    Users of Squid should upgrade to this updated package, which contains     backported patches, and is not vulnerable to these issues.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote host is affected by the vulnerability described in GLSA-200501-25 (Squid: Multiple vulnerabilities)

    Squid contains a vulnerability in the gopherToHTML function     (CAN-2005-0094) and incorrectly checks the 'number of caches' field     when parsing WCCP_I_SEE_YOU messages (CAN-2005-0095). Furthermore the     NTLM code contains two errors. One is a memory leak in the     fakeauth_auth helper (CAN-2005-0096) and the other is a NULL pointer     dereferencing error (CAN-2005-0097). Finally Squid also contains an     error in the ACL parsing code (CAN-2005-0194).
  Impact :

    With the WCCP issue an attacker could cause denial of service by     sending a specially crafted UDP packet. With the Gopher issue an     attacker might be able to execute arbitrary code by enticing a user to     connect to a malicious Gopher server. The NTLM issues could lead to     denial of service by memory consumption or by crashing Squid. The ACL     issue could lead to ACL bypass.
  Workaround :

    There is no known workaround at this time.

An updated Squid package that fixes several security issues is now available.

Squid is a full-featured Web proxy cache.

A buffer overflow flaw was found in the Gopher relay parser. This bug could allow a remote Gopher server to crash the Squid proxy that reads data from it. Although Gopher servers are now quite rare, a malicious web page (for example) could redirect or contain a frame pointing to an attacker's malicious gopher server. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2005-0094 to this issue.

An integer overflow flaw was found in the WCCP message parser. It is possible to crash the Squid server if an attacker is able to send a malformed WCCP message with a spoofed source address matching Squid's 'home router'. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2005-0095 to this issue.

A memory leak was found in the NTLM fakeauth_auth helper. It is possible that an attacker could place the Squid server under high load, causing the NTML fakeauth_auth helper to consume a large amount of memory, resulting in a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2005-0096 to this issue.

A NULL pointer de-reference bug was found in the NTLM fakeauth_auth helper. It is possible for an attacker to send a malformed NTLM type 3 message, causing the Squid server to crash. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2005-0097 to this issue.

A username validation bug was found in squid_ldap_auth. It is possible for a username to be padded with spaces, which could allow a user to bypass explicit access control rules or confuse accounting. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2005-0173 to this issue.

The way Squid handles HTTP responses was found to need strengthening.
It is possible that a malicious web server could send a series of HTTP responses in such a way that the Squid cache could be poisoned, presenting users with incorrect webpages. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2005-0174 and CVE-2005-0175 to these issues.

A bug was found in the way Squid handled oversized HTTP response headers. It is possible that a malicious web server could send a specially crafted HTTP header which could cause the Squid cache to be poisoned, presenting users with incorrect webpages. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2005-0241 to this issue.

A buffer overflow bug was found in the WCCP message parser. It is possible that an attacker could send a malformed WCCP message which could crash the Squid server or execute arbitrary code. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2005-0211 to this issue.

Users of Squid should upgrade to this updated package, which contains backported patches, and is not vulnerable to these issues.

The remote host is missing the patch for the advisory SUSE-SA:2005:006 (squid).


Squid is a feature-rich web-proxy with support for various web-related protocols.
The last two squid updates from February the 1st and 10th fix several vulnerabilities. The impact of them range from remote denial-of-service over cache poisoning to possible remote command execution.
Due to the hugh amount of bugs the vulnerabilities are just summarized here.

CVE-2005-0094 A buffer overflow in the Gopher responses parser leads to memory corruption and usually crash squid.

CVE-2005-0095 An integer overflow in the receiver of WCCP (Web Cache Communication Protocol) messages can be exploited remotely by sending a specially crafted UDP datagram to crash squid.

CVE-2005-0096 A memory leak in the NTLM fakeauth_auth helper for Squid 2.5.STABLE7 and earlier allows remote attackers to cause a denial-of-service due to uncontrolled memory consumption.

CVE-2005-0097 The NTLM component in Squid 2.5.STABLE7 and earlier allows remote attackers to cause a crash od squid by sending a malformed NTLM message. 

CVE-2005-0173 LDAP handles search filters very laxly. This behaviour can be abused to log in using several variants of a login name, possibly bypassing explicit access controls or confusing accounting.

CVE-2005-0175 and CVE-2005-0174 Minor problems in the HTTP header parsing code that can be used for cache poisoning.

CVE-2005-0211 A buffer overflow in the WCCP handling code in Squid 2.5 before 2.5.STABLE7 allows remote attackers to cause a denial-of-service and possibly execute arbitrary code by using a long WCCP packet.

CVE-2005-0241 The httpProcessReplyHeader function in Squid 2.5-STABLE7 and earlier does not properly set the debug context when it is handling 'oversized' HTTP reply headers. The impact is unknown.

'infamous41md' discovered two vulnerabilities in the squid proxy cache server. The first is a buffer overflow in the Gopher response parser which leads to memory corruption and would usually crash squid (CVE-2005-0094). The second is an integer overflow in the receiver of WCCP (Web Cache Communication Protocol) messages. An attacker could send a specially crafted UDP datagram that would cause squid to crash (CVE-2005-0095).

The updated packages have been patched to prevent these problems.

Several vulnerabilities have been discovered in Squid, the internet object cache, the popular WWW proxy cache. The Common Vulnerabilities and Exposures Project identifies the following vulnerabilities :

  - CAN-2005-0094     'infamous41md' discovered a buffer overflow in the     parser for Gopher responses which will lead to memory     corruption and usually crash Squid.

  - CAN-2005-0095

    'infamous41md' discovered an integer overflow in the     receiver of WCCP (Web Cache Communication Protocol)     messages. An attacker could send a specially crafted UDP     datagram that will cause Squid to crash.

The remote Squid caching proxy, according to its version number, is vulnerable to several security flaws :

- There is a buffer overflow issue when handling the reply of a rogue gopher site. To exploit this issue, an attacker would need to use the remote proxy to visit a specially setup gopher site generating malformed replies 

- There is a denial of service vulnerability in the WCCP code of the remote proxy. To exploit this flaw, an attacker would need to guess the IP of the WCCP router used by the proxy and spoof a malformed UDP packet using the router IP address.  There are several flaws in the way that the Squid proxy caches pages.
An attacker exploiting these flaws would be able to poison the Squid
cache. 

According to its version number, the remote Squid caching proxy is affected by several security flaws :

  - There is a buffer overflow when handling the reply of a     rogue gopher site. (CVE-2005-0094)

  - There is a denial of service vulnerability in the WCCP     code of the remote proxy. (CVE-2005-0095)

  - There is a buffer overflow in the WCCP code that may     allow an attacker to execute arbitrary code on the     remote host. (CVE-2005-0211)

  - There is a flaw in the 'squid_ldap_auth' module that may     allow an attacker to bypass authentication and to gain     access to the remote proxy. (CVE-2005-0173)

  - There is a flaw in the way Squid parses HTTP reply     headers. (CVE-2005-0241)

  - There is a weakness that may allow for cache poisoning     via     HTTP response splitting. (CVE-2005-0175)

  - There is a weakness that may allow for cache poisoning     via     crafted malformed headers. (CVE-2005-0174)

Note that this may be a false-positive given the way the Squid team handles releases. Make sure that all the appropriate patches have been applied.

The remote Squid caching proxy, according to its version number, is vulnerable to several security flaws :

- There is a buffer overflow issue when handling the reply of a rogue gopher site. To exploit this issue, an attacker would need to use the remote proxy to visit a specially setup gopher site generating malformed replies 

- There is a denial of service vulnerability in the WCCP code of the remote proxy. To exploit this flaw, an attacker would need to guess the IP of the WCCP router used by the proxy and spoof a malformed UDP packet using the router IP address.  There are several flaws in the way that the Squid proxy caches pages.
An attacker exploiting these flaws would be able to poison the Squid
cache.

ID	Name	Product	Family	Severity
20687	Ubuntu 4.10 : squid vulnerabilities (USN-67-1)	Nessus	Ubuntu Local Security Checks	medium
18953	FreeBSD : squid -- denial of service with forged WCCP messages (5fe7e27a-64cb-11d9-9e1e-c296ac722cb3)	Nessus	FreeBSD Local Security Checks	medium
17176	RHEL 4 : squid (RHSA-2005:060)	Nessus	Red Hat Local Security Checks	high
16416	GLSA-200501-25 : Squid: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	critical
16384	RHEL 2.1 / 3 : squid (RHSA-2005:061)	Nessus	Red Hat Local Security Checks	high
16372	SUSE-SA:2005:006: squid	Nessus	SuSE Local Security Checks	high
16242	Mandrake Linux Security Advisory : squid (MDKSA-2005:014)	Nessus	Mandriva Local Security Checks	medium
16235	Debian DSA-651-1 : squid - buffer overflow, integer overflow	Nessus	Debian Local Security Checks	medium
2537	Squid < 2.5.STABLE8 Multiple Vulnerabilities	Nessus Network Monitor	Web Servers	medium
16190	Squid < 2.5.STABLE8 Multiple Vulnerabilities	Nessus	Firewalls	high
801039	Squid Proxy < 2.5.STABLE8 Gopher, WCCP, and Cache Poisoning Vulnerabilities	Log Correlation Engine	Web Servers	high

Detections

Analytics

CVE-2005-0095

high

Tenable Plugins

medium

medium

high

critical

high

high

medium

medium

medium

high

high