-----BEGIN PGP SIGNED MESSAGE-----

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                squid
        Announcement-ID:        SUSE-SA:2005:006
        Date:                   Thursday, Feb 10th 2005 13:30 MET
        Affected products:      8.1, 8.2, 9.0, 9.1, 9.2
                                SUSE Linux Enterprise Server 8, 9
        Vulnerability Type:     remote command execution
        Severity (1-10):        8
        SUSE default package:   no
        Cross References:       CAN-2005-0094
                                CAN-2005-0095
                                CAN-2005-0096
                                CAN-2005-0097
                                CAN-2005-0173
                                CAN-2005-0174
                                CAN-2005-0175
                                CAN-2005-0211
                                CAN-2005-0241

    Content of this advisory:
        1) security vulnerability resolved:
                + buffer overflow in gopher parser
                + integer overflow in WCCP handling code
                + memory leak in the NTLM fakeauth_auth helper
                + denial-of-service in NTLM component
                + lax LDAP account name handling
                + cache poisoning by malformed HTTP packets
                + cache poisoning by splitted HTTP responses
                + buffer overflow in WCCP handling code
                + httpProcessReplyHeader function does not
                  properly set the debug context
           problem description
        2) solution/workaround
        3) special instructions and notes
        4) package location and checksums
        5) pending vulnerabilities, solutions, workarounds:
        6) standard appendix (further information)

______________________________________________________________________________

1) problem description, brief discussion

    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.
    
        CAN-2005-0094
                A buffer overflow in the Gopher responses parser leads
                to memory corruption and usually crash squid.

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

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

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

        CAN-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.
        
        CAN-2005-0175 and CAN-2005-0174
                Minor problems in the HTTP header parsing code that
                can be used for cache poisoning.
        
        CAN-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.
                
        CAN-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.

        
2) solution/workaround

    There is no workaround known.

    
3) special instructions and notes

    Please make sure squid is restarted after the update.
    Execute 'rcsquid restart' as user root.
    

4) package location and checksums

    Download the update package for your distribution and verify its
    integrity by the methods listed in section 3) of this announcement.
    Then, install the package using the command "rpm -Fhv file.rpm" to apply
    the update.
    Our maintenance customers are being notified individually. The packages
    are being offered for installation from the maintenance web.

    
    x86 Platform:

    SUSE Linux 9.2:
          1002a1c5d0841a698e76f6e9879b91e9
    patch rpm(s):
          10f2257aa1238835ede8cd820a16c684
    source rpm(s):
          9d54a80127df60cad2b254c1e4a434b8

    SUSE Linux 9.1:
          95dc251f27d87496e73b74f15c8030c6
    patch rpm(s):
          f8b5486243cc2369c8f577fdc7ff3de2
    source rpm(s):
          d8d805a1062e9759c21cd19affdcd3b5

    SUSE Linux 9.0:
          8e94548f94fc7bf7f07ae2005fceb47e
    patch rpm(s):
          eec32d15c7a3ae21accb69d0c02cc8b2
    source rpm(s):
          6d8a366925335c44a0727cf53a0062cf

    SUSE Linux 8.2:
          7457d43267f88b26faf83695c87eaf89
    patch rpm(s):
          8393c0a5791f0390030d86b71337c96e
    source rpm(s):
          189f57b8b006afdf3e13da058518491b

    SUSE Linux 8.1:
          177fc495629e0b4d2c2e3f5fd92a8ed4
    patch rpm(s):
          2bfe53711f0a4937760be18a5fe77189
    source rpm(s):
          148c812936f32d9dfb14684f081efc8d



    x86-64 Platform:

    SUSE Linux 9.2:
          5ea1d0c4217095aa6416fb5524d4f5ea
    patch rpm(s):
          44a8568ac14a2799cd2424088ab48a15
    source rpm(s):
          9d54a80127df60cad2b254c1e4a434b8

    SUSE Linux 9.1:
          928be9deeadb7d0c5abb02518225fd0b
    patch rpm(s):
          48acc169a1d84e77ad861517b12a49f6
    source rpm(s):
          e3a8028984ea67f0b9becfd8d00e86eb

    SUSE Linux 9.0:
          f2501c3be9d3c1f70e65fe41628ef494
    patch rpm(s):
          3b77d4262e1e8cbc4c71e8ec4aa48162
    source rpm(s):
          4f3fcad35b37467922a9d710c2ea84a2

______________________________________________________________________________

5) Pending vulnerabilities in SUSE Distributions and Workarounds:

    Please see the SUSE Security Summary Report.
______________________________________________________________________________

6) standard appendix: authenticity verification, additional information

  - Package authenticity verification:

    SUSE update packages are available on many mirror ftp servers all over
    the world. While this service is being considered valuable and important
    to the free and open source software community, many users wish to be
    sure about the origin of the package and its content before installing
    the package. There are two verification methods that can be used
    independently from each other to prove the authenticity of a downloaded
    file or rpm package:
    1) md5sums as provided in the (cryptographically signed) announcement.
    2) using the internal gpg signatures of the rpm package.

    1) execute the command
        md5sum 
       after you downloaded the file from a SUSE ftp server or its mirrors.
       Then, compare the resulting md5sum with the one that is listed in the
       announcement. Since the announcement containing the checksums is
       cryptographically signed (usually using the key security@suse.de),
       the checksums show proof of the authenticity of the package.
       We recommend against subscribing to security lists that cause the
       e-mail message containing the announcement to be modified
       so that the signature does not match after transport through the mailing
       list software.
       Downsides: You must be able to verify the authenticity of the
       announcement in the first place. If RPM packages are being rebuilt
       and a new version of a package is published on the ftp server, all
       md5 sums for the files are useless.

    2) rpm package signatures provide an easy way to verify the authenticity
       of an rpm package. Use the command
        rpm -v --checksig 
       to verify the signature of the package, where  is the
       file name of the rpm package that you have downloaded. Of course,
       package authenticity verification can only target an uninstalled rpm
       package file.
       Prerequisites:
        a) gpg is installed
        b) The package is signed using a certain key. The public part of this
           key must be installed by the gpg program in the directory
           ~/.gnupg/ under the user's home directory who performs the
           signature verification (usually root). You can import the key
           that is used by SUSE in rpm packages for SUSE Linux by saving
           this announcement to a file ("announcement.txt") and
           running the command (do "su -" to be root):
            gpg --batch; gpg < announcement.txt | gpg --import
           SUSE Linux distributions version 7.1 and thereafter install the
           key "build@suse.de" upon installation or upgrade, provided that
           the package gpg is installed. The file containing the public key
           is placed at the top-level directory of the first CD (pubring.gpg)
           and at  .


  - SUSE runs two security mailing lists to which any interested party may
    subscribe:

    suse-security@suse.com
        -   general/linux/SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an email to
                .

    suse-security-announce@suse.com
        -   SUSE's announce-only mailing list.
            Only SUSE's security announcements are sent to this list.
            To subscribe, send an email to
                .

    For general information or the frequently asked questions (faq)
    send mail to:
         or
         respectively.

    ====================================================================    SUSE's security contact is  or .
    The  public key is listed below.
    ====================================================================