blob: bcdf616b9437a0535a3c43f28010a9f1550acb7c [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<glsa id="200502-04">
<title>Squid: Multiple vulnerabilities</title>
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.
<product type="ebuild">squid</product>
<announced>February 02, 2005</announced>
<revised>February 02, 2005: 02</revised>
<package name="net-proxy/squid" auto="yes" arch="*">
<unaffected range="ge">2.5.7-r5</unaffected>
<vulnerable range="lt">2.5.7-r5</vulnerable>
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:
<li>Buffer overflow when handling WCCP recvfrom()
<li>Loose checking of HTTP headers (CAN-2005-0173 and
<li>Incorrect handling of LDAP login names with spaces
<impact type="normal">
An attacker could exploit:
<li>the WCCP buffer overflow to cause Denial of Service.</li>
<li>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
<li>the LDAP issue to login with several variations of the same login
name, leading to log poisoning.</li>
There is no known workaround at this time.
All Squid users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose &quot;&gt;=net-proxy/squid-2.5.7-r5&quot;</code>
<uri link="">CAN-2005-0173</uri>
<uri link="">CAN-2005-0174</uri>
<uri link="">CAN-2005-0175</uri>
<uri link="">CAN-2005-0211</uri>
<metadata tag="submitter" timestamp="Sun, 30 Jan 2005 20:28:30 +0000">
<metadata tag="bugReady" timestamp="Wed, 2 Feb 2005 12:30:09 +0000">