-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: curl, wget
Announcement ID: SUSE-SA:2005:063
Date: Mon, 24 Oct 2005 16:00:00 +0000
Affected Products: SUSE LINUX 10.0
SUSE LINUX 9.3
SUSE LINUX 9.2
SUSE LINUX 9.1
SUSE Linux Enterprise Server 9
Novell Linux Desktop 9
Open Enterprise Server
Vulnerability Type: remote code execution
Severity (1-10): 7
SUSE Default Package: yes
Cross-References: CVE-2005-3185
Content of This Advisory:
1) Security Vulnerability Resolved:
stack based buffer overflow in NTLM authentication
Problem Description
2) Solution or Work-Around
3) Special Instructions and Notes
4) Package Location and Checksums
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
See SUSE Security Summary Report.
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
This update fixes a stack-based buffer overflow in the NTLM
authentication code used by the file download tools/libraries curl
and wget that can be triggered by using a long user or domain name
(also works with HTTP redirects).
By exploiting this bug by using a malicious server an attacker may
be able to execute arbitrary code with the privileges of the entity
running the process locally. (CVE-2005-3185)
This affects both curl/libcurl and wget >= 1.10. wget copied the code
from libcurl, making this effectively the same problem.
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
Please close and restart all running instances of programs using
libcurl 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.
x86 Platform:
SUSE LINUX 10.0:
8f5ea41e7b4e80798c960790bb93e603
8e59e94e8745f0916ed00a7040d4e597
2a91b99e5adfd78b2e9c6a3b03bcc67d
SUSE LINUX 9.3:
dc1b2e8dc509adca503b7f2e7724be49
937855b131da29025f48cab5880a91ea
556ba3000c278fecfec9c24b1b5ce44f
SUSE LINUX 9.2:
2b21dc3b9877f45602191cc33c695734
77802b5fb55775fd00b1e7e71cb03aab
SUSE LINUX 9.1:
8f18c55e56f560e641173b7ca96a13a6
07b00ace15bc16b4e6ee878cb4703f34
Power PC Platform:
SUSE LINUX 10.0:
b69c93ed024d1887cb1fafa9140c7235
1102f6dd51867fb06921e1b35354821d
ba717462ca2644628296cb473f228926
x86-64 Platform:
SUSE LINUX 10.0:
e42d1a8642003893cc2656effc2befae
f29e8a213abc2a6df3c514849dd58f45
531e4e3a333cd7a869bce42d4f284c34
d11fd9298ca5a0d6009810afc02ffa00
4025598d1a4d5c1f3bfb288df9ba62e0
SUSE LINUX 9.3:
8064b387585923ca8bf897294d6e0750
c6174cc85a1a8a7ae0aef33703b255ab
d4da6969e3c7c08c2387bf2f491ae6b2
d6db8fa9847c74194db4b11508aa81e5
62373d0f58db04c85d6d558002b61439
SUSE LINUX 9.2:
8176f04bcc6b8a5b5e6730570d71e1dc
77ca0f684608cd05d6680b71a60f3d2b
225eaed129a89f522099a4dd05fbd92f
SUSE LINUX 9.1:
c7e53c0f5b9e176ea517b2cd6e212b7b
Sources:
SUSE LINUX 10.0:
dd327d44a1e34dc62557d731191d8eaa
501302472341f049f32c26158857afe4
620602e6c0d6745278570b049dc62d6f
SUSE LINUX 9.3:
f28644961a98a391fcd4f9c220d95976
115bbe666fc6d170f0209bf08d415e94
201a3d45868f65590bb78bb80f40c1f5
SUSE LINUX 9.2:
9c3f454a7d31bddee04df39a6b10052c
f5249c9853905e77323c6febfe319809
SUSE LINUX 9.1:
c64049955adb7067312b8716e61e2819
9bb9bd0870ab5a6a76e5da583323ca98
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
https://www.suse.com:443/
______________________________________________________________________________
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
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.
====================================================================
