RHSA-2005:060: squid security update

Squid is a full-featured Web proxy cache.A buffer overflow flaw was found in the Gopher relay parser. This bugcould allow a remote Gopher server to crash the Squid proxy that reads datafrom it. Although Gopher servers are now quite rare, a malicious webpage(for example) could redirect or contain a frame pointing to an attacker'smalicious 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 ispossible to crash the Squid server if an attacker is able to send amalformed 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 fakeauthauth helper. It is possiblethat an attacker could place the Squid server under high load, causing theNTML fakeauthauth helper to consume a large amount of memory, resulting ina 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 fakeauthauth helper.It is possible for an attacker to send a malformed NTLM type 3 message,causing the Squid server to crash. The Common Vulnerabilities andExposures project (cve.mitre.org) has assigned the name CAN-2005-0097 tothis issue.A username validation bug was found in squidldapauth. It is possible fora username to be padded with spaces, which could allow a user to bypassexplicit access control rules or confuse accounting. The CommonVulnerabilities and Exposures project (cve.mitre.org) has assigned the nameCAN-2005-0173 to this issue.The way Squid handles HTTP responses was found to need strengthening. It ispossible that a malicious Web server could send a series of HTTP responsesin such a way that the Squid cache could be poisoned, presenting users withincorrect webpages. The Common Vulnerabilities and Exposures project(cve.mitre.org) has assigned the names CAN-2005-0174 and CAN-2005-0175 tothese 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 craftedHTTP header which could cause the Squid cache to be poisoned, presentingusers with incorrect webpages. The Common Vulnerabilities and Exposuresproject (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 possiblethat an attacker could send a malformed WCCP message which could crash theSquid server or execute arbitrary code. The Common Vulnerabilities andExposures project (cve.mitre.org) has assigned the name CAN-2005-0211to this issue.Users of Squid should upgrade to this updated package, which containsbackported patches, and is not vulnerable to these issues.