-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                gzip
        Announcement ID:        SUSE-SA:2006:056
        Date:                   Tue, 26 Sep 2006 15:32:33 +0000
        Affected Products:      SLE SDK 10
                                SUSE LINUX 10.1
                                SUSE LINUX 10.0
                                SUSE LINUX 9.3
                                SUSE LINUX 9.2
                                SuSE Linux Desktop 1.0
                                SuSE Linux Enterprise Server 8
                                SUSE SLES 10
                                SUSE SLES 9
                                UnitedLinux 1.0
        Vulnerability Type:     remote system compromise
        Severity (1-10):        6
        SUSE Default Package:   yes
        Cross-References:       CVE-2006-4334,CVE-2006-4335,CVE-2006-4336,
                                CVE-2006-4337,CVE-2006-4338

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             buffer overflows, infinite loops
           Problem Description
        2) Solution or Work-Around
        3) Special Instructions and Notes
        4) Package Location and Checksums
        5) Pending Vulnerabilities, Solutions, and Work-Arounds:
            none
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   The gzip tool does not handle some specific values correctly when unpacking
   archives. This leads to vulnerabilities like buffer overflows or infinite
   loops.
   
   Various different programs like mail clients, file explorer, etc. use gzip
   and if a user can be deveived to unpack the archive of an attacker these
   bugs can lead to remote system compromise.
   
   Thanks to Tavis Ormandy, Google Security Team for informing us about this
   issue.

2) Solution or Work-Around

   The is no work-around known.

3) Special Instructions and Notes

   none

4) Package Location and Checksums

   The preferred method for installing security updates is to use the YaST
   Online Update (YOU) tool. YOU detects which updates are required and
   automatically performs the necessary steps to verify and install them.
   Alternatively, download the update packages for your distribution manually
   and verify their integrity by the methods listed in Section 6 of this
   announcement. Then install the packages using the command

     rpm -Fhv 

   to apply the update, replacing  with the filename of the
   downloaded RPM package.

   
   x86 Platform:
   
   SUSE LINUX 10.1:
             dc3d0d1fa04f309155188d456339e320
   
   SUSE LINUX 10.0:
             fa214e77cac58482b03a39aa3637402f
   
   SUSE LINUX 9.3:
             93c268c56d6f2bfb97fb1362440619ff
   
   SUSE LINUX 9.2:
             9ce8e3d5dda60f5c0226e1003555e7e3
   
   Power PC Platform:
   
   SUSE LINUX 10.1:
             e5216ebf301cc076117d24b1d641d666
   
   SUSE LINUX 10.0:
             70fad9dec1124d6e2a18cddb56542e21
   
   x86-64 Platform:
   
   SUSE LINUX 10.1:
             bc88120404ee14a4f85869bf7b664c23
   
   SUSE LINUX 10.0:
             9bac8a94f263b70fcb0188b8fe61b51a
   
   SUSE LINUX 9.3:
             e99894cc66b479b026a8d6ab8f3d4bee
   
   SUSE LINUX 9.2:
             7f58b2c8124e895b5bbbf24e92f5701a
   
   Sources:
   
   SUSE LINUX 10.1:
             ccc806bead84a51395e24d03e1b08132
   
   SUSE LINUX 10.0:
             8d38b0719a591ac7c41aa35062ca8f2e
   
   SUSE LINUX 9.3:
             1c7511c702371171e4a940e6c6740c35
   
   SUSE LINUX 9.2:
             81243003d7d3b397d7043a74059c5d7f
   
   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web:
   
   
______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Work-Arounds:

   none
______________________________________________________________________________

6) Authenticity Verification and Additional Information

  - Announcement authenticity verification:

    SUSE security announcements are published via mailing lists and on Web
    sites. The authenticity and integrity of a SUSE security announcement is
    guaranteed by a cryptographic signature in each announcement. All SUSE
    security announcements are published with a valid signature.

    To verify the signature of the announcement, save it as text into a file
    and run the command

      gpg --verify 

    replacing  with the name of the file where you saved the
    announcement. The output for a valid signature looks like:

      gpg: Signature made  using RSA key ID 3D25D3D9
      gpg: Good signature from "SuSE Security Team "

    where  is replaced by the date the document was signed.

    If the security team's key is not contained in your key ring, you can
    import it from the first installation CD. To import the key, use the
    command

      gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc

  - Package authenticity verification:

    SUSE update packages are available on many mirror FTP servers all over the
    world. While this service is considered valuable and important to the free
    and open source software community, the authenticity and the integrity of
    a package needs to be verified to ensure that it has not been tampered
    with.

    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) Using the internal gpg signatures of the rpm package
    2) MD5 checksums as provided in this announcement

    1) The internal 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, replacing  with the
       filename of the RPM package downloaded. The package is unmodified if it
       contains a valid signature from build@suse.de with the key ID 9C800ACA.

       This key is automatically imported into the RPM database (on
       RPMv4-based distributions) and the gpg key ring of 'root' during
       installation. You can also find it on the first installation CD and at
       the end of this announcement.

    2) If you need an alternative means of verification, use the md5sum
       command to verify the authenticity of the packages. 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
       SUSE security announcement. Because the announcement containing the
       checksums is cryptographically signed (by security@suse.de), the
       checksums show proof of the authenticity of the package if the
       signature of the announcement is valid. Note that the md5 sums
       published in the SUSE Security Announcements are valid for the
       respective packages only. Newer versions of these packages cannot be
       verified.

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

    suse-security@suse.com
        -   General Linux and SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an e-mail 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 e-mail to
                .

    For general information or the frequently asked questions (FAQ),
    send mail to  or
    .

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

SuSE: 2006-056: gzip Security Update

September 26, 2006
The gzip tool does not handle some specific values correctly when unpacking The gzip tool does not handle some specific values correctly when unpacking archives

Summary


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                gzip
        Announcement ID:        SUSE-SA:2006:056
        Date:                   Tue, 26 Sep 2006 15:32:33 +0000
        Affected Products:      SLE SDK 10
                                SUSE LINUX 10.1
                                SUSE LINUX 10.0
                                SUSE LINUX 9.3
                                SUSE LINUX 9.2
                                SuSE Linux Desktop 1.0
                                SuSE Linux Enterprise Server 8
                                SUSE SLES 10
                                SUSE SLES 9
                                UnitedLinux 1.0
        Vulnerability Type:     remote system compromise
        Severity (1-10):        6
        SUSE Default Package:   yes
        Cross-References:       CVE-2006-4334,CVE-2006-4335,CVE-2006-4336,
                                CVE-2006-4337,CVE-2006-4338

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             buffer overflows, infinite loops
           Problem Description
        2) Solution or Work-Around
        3) Special Instructions and Notes
        4) Package Location and Checksums
        5) Pending Vulnerabilities, Solutions, and Work-Arounds:
            none
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   The gzip tool does not handle some specific values correctly when unpacking
   archives. This leads to vulnerabilities like buffer overflows or infinite
   loops.
   
   Various different programs like mail clients, file explorer, etc. use gzip
   and if a user can be deveived to unpack the archive of an attacker these
   bugs can lead to remote system compromise.
   
   Thanks to Tavis Ormandy, Google Security Team for informing us about this
   issue.

2) Solution or Work-Around

   The is no work-around known.

3) Special Instructions and Notes

   none

4) Package Location and Checksums

   The preferred method for installing security updates is to use the YaST
   Online Update (YOU) tool. YOU detects which updates are required and
   automatically performs the necessary steps to verify and install them.
   Alternatively, download the update packages for your distribution manually
   and verify their integrity by the methods listed in Section 6 of this
   announcement. Then install the packages using the command

     rpm -Fhv 

   to apply the update, replacing  with the filename of the
   downloaded RPM package.

   
   x86 Platform:
   
   SUSE LINUX 10.1:
             dc3d0d1fa04f309155188d456339e320
   
   SUSE LINUX 10.0:
             fa214e77cac58482b03a39aa3637402f
   
   SUSE LINUX 9.3:
             93c268c56d6f2bfb97fb1362440619ff
   
   SUSE LINUX 9.2:
             9ce8e3d5dda60f5c0226e1003555e7e3
   
   Power PC Platform:
   
   SUSE LINUX 10.1:
             e5216ebf301cc076117d24b1d641d666
   
   SUSE LINUX 10.0:
             70fad9dec1124d6e2a18cddb56542e21
   
   x86-64 Platform:
   
   SUSE LINUX 10.1:
             bc88120404ee14a4f85869bf7b664c23
   
   SUSE LINUX 10.0:
             9bac8a94f263b70fcb0188b8fe61b51a
   
   SUSE LINUX 9.3:
             e99894cc66b479b026a8d6ab8f3d4bee
   
   SUSE LINUX 9.2:
             7f58b2c8124e895b5bbbf24e92f5701a
   
   Sources:
   
   SUSE LINUX 10.1:
             ccc806bead84a51395e24d03e1b08132
   
   SUSE LINUX 10.0:
             8d38b0719a591ac7c41aa35062ca8f2e
   
   SUSE LINUX 9.3:
             1c7511c702371171e4a940e6c6740c35
   
   SUSE LINUX 9.2:
             81243003d7d3b397d7043a74059c5d7f
   
   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web:
   
   
______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Work-Arounds:

   none
______________________________________________________________________________

6) Authenticity Verification and Additional Information

  - Announcement authenticity verification:

    SUSE security announcements are published via mailing lists and on Web
    sites. The authenticity and integrity of a SUSE security announcement is
    guaranteed by a cryptographic signature in each announcement. All SUSE
    security announcements are published with a valid signature.

    To verify the signature of the announcement, save it as text into a file
    and run the command

      gpg --verify 

    replacing  with the name of the file where you saved the
    announcement. The output for a valid signature looks like:

      gpg: Signature made  using RSA key ID 3D25D3D9
      gpg: Good signature from "SuSE Security Team "

    where  is replaced by the date the document was signed.

    If the security team's key is not contained in your key ring, you can
    import it from the first installation CD. To import the key, use the
    command

      gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc

  - Package authenticity verification:

    SUSE update packages are available on many mirror FTP servers all over the
    world. While this service is considered valuable and important to the free
    and open source software community, the authenticity and the integrity of
    a package needs to be verified to ensure that it has not been tampered
    with.

    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) Using the internal gpg signatures of the rpm package
    2) MD5 checksums as provided in this announcement

    1) The internal 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, replacing  with the
       filename of the RPM package downloaded. The package is unmodified if it
       contains a valid signature from build@suse.de with the key ID 9C800ACA.

       This key is automatically imported into the RPM database (on
       RPMv4-based distributions) and the gpg key ring of 'root' during
       installation. You can also find it on the first installation CD and at
       the end of this announcement.

    2) If you need an alternative means of verification, use the md5sum
       command to verify the authenticity of the packages. 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
       SUSE security announcement. Because the announcement containing the
       checksums is cryptographically signed (by security@suse.de), the
       checksums show proof of the authenticity of the package if the
       signature of the announcement is valid. Note that the md5 sums
       published in the SUSE Security Announcements are valid for the
       respective packages only. Newer versions of these packages cannot be
       verified.

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

    suse-security@suse.com
        -   General Linux and SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an e-mail 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 e-mail to
                .

    For general information or the frequently asked questions (FAQ),
    send mail to  or
    .

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

References

Severity

Related News