Share your story
The central voice for Linux and Open Source security news
Home News Topics Advisories HOWTOs Features Newsletters About Register

Sign up!
EnGarde Community
What is the most important Linux security technology?
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
White Papers
Featured Blogs
All About Linux
DanWalsh LiveJournal
Latest Newsletters
Linux Advisory Watch: March 27th, 2015
Linux Security Week: March 23rd, 2015
LinuxSecurity Newsletters
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

SuSE: squid (SUSE-SA:2005:006) Print E-mail
User Rating:      How can I rate this item?
Posted by Benjamin D. Thomas   
SuSE 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.

                        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

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

                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.

                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

                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. 

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

    SUSE Linux 9.1:
    patch rpm(s):
    source rpm(s):

    SUSE Linux 9.0:
    patch rpm(s):
    source rpm(s):

    SUSE Linux 8.2:
    patch rpm(s):
    source rpm(s):

    SUSE Linux 8.1:
    patch rpm(s):
    source rpm(s):

    x86-64 Platform:

    SUSE Linux 9.2:
    patch rpm(s):
    source rpm(s):

    SUSE Linux 9.1:
    patch rpm(s):
    source rpm(s):

    SUSE Linux 9.0:
    patch rpm(s):
    source rpm(s):


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
       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,
       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.
        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 "" 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
        -   general/linux/SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an email to
        -   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:

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

    The information in this advisory may be distributed or reproduced,
    provided that the advisory is not modified in any way. In particular,
    it is desired that the clear-text signature shows proof of the
    authenticity of the text.
    SUSE Linux AG makes no warranties of any kind whatsoever with respect
    to the information contained in this security advisory.
< Prev   Next >


Latest Features
Peter Smith Releases Linux Network Security Online
Securing a Linux Web Server
Password guessing with Medusa 2.0
Password guessing as an attack vector
Squid and Digest Authentication
Squid and Basic Authentication
Demystifying the Chinese Hacking Industry: Earning 6 Million a Night
Free Online security course (LearnSIA) - A Call for Help
What You Need to Know About Linux Rootkits
Review: A Practical Guide to Fedora and Red Hat Enterprise Linux - Fifth Edition
Yesterday's Edition
FBI Quietly Removes Recommendation To Encrypt Your Phone
And the prize for LEAST SECURE BROWSER goes to ... Chrome!
Partner Sponsor

Community | HOWTOs | Blogs | Features | Book Reviews | Networking
 Security Projects |  Latest News |  Newsletters |  SELinux |  Privacy |  Home
 Hardening |   About Us |   Advertise |   Legal Notice |   RSS |   Guardian Digital
(c)Copyright 2015 Guardian Digital, Inc. All rights reserved.