Squid: Multiple vulnerabilities

Squid: Multiple vulnerabilities Squid contains vulnerabilities in the code handling WCCP, HTTP and LDAP which could lead to Denial of Service, access control bypass, web cache and log poisoning. squid 2005-02-02 2005-02-02 79495 78776 80201 80341 remote 2.5.7-r5 2.5.7-r5

Squid is a full-featured Web proxy cache designed to run on Unix systems. It supports proxying and caching of HTTP, FTP, and other protocols, as well as SSL support, cache hierarchies, transparent caching, access control lists and many other features.

Squid contains several vulnerabilities:

Buffer overflow when handling WCCP recvfrom() (CAN-2005-0211).
Loose checking of HTTP headers (CAN-2005-0173 and CAN-2005-0174).
Incorrect handling of LDAP login names with spaces (CAN-2005-0175).

An attacker could exploit:

the WCCP buffer overflow to cause Denial of Service.
the HTTP header parsing vulnerabilities to inject arbitrary response data, potentially leading to content spoofing, web cache poisoning and other cross-site scripting or HTTP response splitting attacks.
the LDAP issue to login with several variations of the same login name, leading to log poisoning.

There is no known workaround at this time.

All Squid users should upgrade to the latest version:


    # emerge --sync
    # emerge --ask --oneshot --verbose ">=net-proxy/squid-2.5.7-r5"

CAN-2005-0173 CAN-2005-0174 CAN-2005-0175 CAN-2005-0211 jaervosz jaervosz