-----BEGIN PGP SIGNED MESSAGE-----
______________________________________________________________________________
SUSE Security Announcement
Package: squid
Announcement ID: SUSE-SA:2005:053
Date: Fri, 16 Sep 2005 14:28:00 +0000
Affected Products: 9.0, 9.1, 9.2, 9.3
SUSE Linux Enterprise Server 8, 9
Open Enterprise Server 9
Vulnerability Type: remote denial of service
Severity (1-10): 4
SUSE Default Package: no
Cross-References: CAN-2005-2794
CAN-2005-2796
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 Workarounds:
none
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
This update of the Squid web-proxy fixes two remotely exploitable denial
of service vulnerabilities.
One can be triggered by aborting a request (CAN-2005-2794) due to a faulty
assertion.
The other one occurs in sslConnectTimeout while handling malformated
requests (CAN-2005-2796).
The latter one does not affect SUSE LINUX 9.3.
2) Solution or Workaround
There are no workarounds known.
3) Special Instructions and Notes
Please restart the Squid web-proxy after the update.
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.
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web.
x86 Platform:
SUSE Linux 9.3:
eea572b10ecf573753af16ecf1fbdaa7
patch rpm(s):
becf331a849332d734d72f90801d8338
source rpm(s):
8c0ffeccd0c8fd64418164f275adbd27
SUSE Linux 9.2:
93720922d4f7ae4370b2c4e493fae592
patch rpm(s):
9e4d07f1f11c8c1cbf7564c8d2164ca7
source rpm(s):
236cb11582b4983350ef81e5e8508c39
SUSE Linux 9.1:
dc9848a817367dfe278a6f3954c6677f
patch rpm(s):
5c534d9df125a3ff02c5fa32bf216f64
source rpm(s):
4dd683495e578ec59bd34260caf9a565
SUSE Linux 9.0:
6d094da21806166dde5f6da8307ca2a2
patch rpm(s):
02172274b15a28b918c54d470203d029
source rpm(s):
3cfae65a6cee24e6cfe8adc4226fa601
x86-64 Platform:
SUSE Linux 9.3:
d07ae04a018a3abb082cd0b130c145a0
patch rpm(s):
cbcb39ccc9ee0340692ae3cf048453ff
source rpm(s):
8c0ffeccd0c8fd64418164f275adbd27
SUSE Linux 9.2:
915b0b2955f878a2e89b171d1335274c
patch rpm(s):
c488ab4031de911b6675a785a4d2a4dd
source rpm(s):
236cb11582b4983350ef81e5e8508c39
SUSE Linux 9.1:
6fc9746898681ee217f884f6aaca8e68
patch rpm(s):
37ada616c159242b53e2dfbf5f94597c
source rpm(s):
310321fd1232ea45ccb06fd5b24ba664
SUSE Linux 9.0:
f39071c7802d8bb77ed00038e095a6af
patch rpm(s):
05f996332331ddebf848cc2726fcbc87
source rpm(s):
3c7e8fc9a5e0cf4c6638d57fed2fdf53
______________________________________________________________________________
5) Pending Vulnerabilities, Solutions, and Workarounds:
See SUSE Security Summary Report.
______________________________________________________________________________
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.
====================================================================
