- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                        GLSA 200502-04:02
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

  Severity: Normal
     Title: Squid: Multiple vulnerabilities
      Date: February 02, 2005
   Updated: February 02, 2005
      Bugs: #79495, #78776, #80201, #80341
        ID: 200502-04:02

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
========

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.

Background
==========

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.

Affected packages
=================

    -------------------------------------------------------------------
     Package          /  Vulnerable  /                      Unaffected
    -------------------------------------------------------------------
  1  www-proxy/squid     < 2.5.7-r5                        >= 2.5.7-r5

Description
===========

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).

Impact
======

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.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All Squid users should upgrade to the latest version:

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

References
==========

  [ 1 ] CAN-2005-0173
        http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-0173
  [ 2 ] CAN-2005-0174
        http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-0174
  [ 3 ] CAN-2005-0175
        http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-0175
  [ 4 ] CAN-2005-0211
        http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-0211

Availability
============

This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

  http://security.gentoo.org/glsa/glsa-200502-04.xml

Concerns?
=========

Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
http://bugs.gentoo.org.

License
=======

Copyright 2005 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

http://creativecommons.org/licenses/by-sa/2.0