squid (denial of service)

Date: Tue, 23 Jan 2007 11:07:29 +0100
From: Thomas Biege
To: suse-security-announce@suse.com
Subject: SUSE Security Announcement: squid (SUSE-SA:2007:012)


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

______________________________________________________________________________

SUSE Security Announcement

Package: squid
Announcement ID: SUSE-SA:2007:012
Date: Tue, 23 Jan 2007 09:00:00 +0000
Affected Products: SUSE LINUX 9.3
SUSE LINUX 10.0
SUSE LINUX 10.1
openSUSE 10.2
UnitedLinux 1.0
SuSE Linux Enterprise Server 8
SuSE Linux Openexchange Server 4
SuSE Linux Standard Server 8
SuSE Linux School Server
SUSE LINUX Retail Solution 8
SUSE SLES 9
Open Enterprise Server
Novell Linux POS 9
SUSE SLED 10
SUSE SLES 10
Vulnerability Type: remote denial of service
Severity (1-10): 4
SUSE Default Package: no
Cross-References: CVE-2007-0247
CVE-2007-0248

Content of This Advisory:
1) Security Vulnerability Resolved:
remote denial of service
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

This update fixes a remotely exploitable denial-of-service
bug in squid that can be triggered by using special ftp://
URLs. (CVE-2007-0247)
Additionally the 10.2 package needed a fix for another DoS
bug (CVE-2007-0248) and for max_user_ip handling in
ntlm_auth.


2) Solution or Work-Around

No temporary work-around known.


3) Special Instructions and Notes

Restart squid.


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:

openSUSE 10.2:
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/i586/squid-2.6.STABLE6-0.4.i586.rpm
c1a38e8dc8301158fe717a9115e60001

SUSE LINUX 10.1:
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/i586/squid-2.5.STABLE12-18.6.i586.rpm
b390a43cd014988f3444fc8a3f89af7d

SUSE LINUX 10.0:
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/squid-2.5.STABLE10-5.5.i586.rpm
171ae4d1ae9941da3641391f0cbb020e

SUSE LINUX 9.3:
ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/squid-2.5.STABLE9-4.9.i586.rpm
5abca23e37cee2bf20085951b8a59953

Power PC Platform:

openSUSE 10.2:
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/ppc/squid-2.6.STABLE6-0.4.ppc.rpm
ffb0c8fe4086a913fede3cba0f1b473c

SUSE LINUX 10.1:
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/squid-2.5.STABLE12-18.6.ppc.rpm
bec76f3f1c4a445801117f696d438925

SUSE LINUX 10.0:
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/squid-2.5.STABLE10-5.5.ppc.rpm
87fc216ed79eee0d5eecf2ba24d4adfe

x86-64 Platform:

openSUSE 10.2:
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/x86_64/squid-2.6.STABLE6-0.4.x86_64.rpm
6b37f676418485c52d262cc8f17347f0

SUSE LINUX 10.1:
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/squid-2.5.STABLE12-18.6.x86_64.rpm
ddc9aaba2e99eeb2d8215acf799b8ecb

SUSE LINUX 10.0:
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/squid-2.5.STABLE10-5.5.x86_64.rpm
100ed655a1fbdcf4a8ed1bd98598e2bb

SUSE LINUX 9.3:
ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/squid-2.5.STABLE9-4.9.x86_64.rpm
599d0bb6f1cd872816eb371abf24a44e

Sources:

openSUSE 10.2:
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/src/squid-2.6.STABLE6-0.4.src.rpm
8467df81f96919f3a1c6d55905581735

SUSE LINUX 10.1:
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/src/squid-2.5.STABLE12-18.6.src.rpm
5da1a897fdb953cb3f9801d0eda1899b

SUSE LINUX 10.0:
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/src/squid-2.5.STABLE10-5.5.src.rpm
794090e751edceb8355c4706a28c2aa5

SUSE LINUX 9.3:
ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/src/squid-2.5.STABLE9-4.9.src.rpm
6c6c1a9a0e0db47a3336d51551a859e9

Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:

UnitedLinux 1.0
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

SuSE Linux Openexchange Server 4
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

Open Enterprise Server
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

Novell Linux POS 9
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

SuSE Linux Enterprise Server 8
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

SuSE Linux Standard Server 8
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

SuSE Linux School Server
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

SUSE LINUX Retail Solution 8
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

SUSE SLES 10
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

SUSE SLED 10
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

SUSE SLES 9
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

______________________________________________________________________________

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:

opensuse-security@opensuse.org
- 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
.

=====================================================================
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, the
clear text signature should show proof of the authenticity of the text.

SUSE Linux Products GmbH provides no warranties of any kind whatsoever
with respect to the information contained in this security advisory.

Type Bits/KeyID Date User ID
pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key