infamous41md@hotpop.com reported a vulnerability in libcurl, the
HTTP/FTP retrieval library. This library is used by lots of programs,
including YaST2 and PHP4.
______________________________________________________________________________
SUSE Security Announcement
Package: curl
Announcement-ID: SUSE-SA:2005:011
Date: Mon, 28 Feb 2005 12:00:00 +0000
Affected products: 9.1, 9.2
SUSE Linux Enterprise Server 9
Novell Linux Desktop 9
Vulnerability Type: remote code execution
Severity (1-10): 10
SUSE default package: yes
Cross References: CAN-2005-0490
Content of this advisory:
1) security vulnerability resolved:
buffer overflow in curl NTLM authentication
problem description
2) solution/workaround
3) special instructions and notes
4) package location and checksums
5) pending vulnerabilities, solutions, workarounds:
See SUSE Security Summary Report.
6) standard appendix (further information)
______________________________________________________________________________
1) problem description, brief discussion
infamous41md@hotpop.com reported a vulnerability in libcurl, the
HTTP/FTP retrieval library. This library is used by lots of programs,
including YaST2 and PHP4.
The NTLM authorization in curl had a buffer overflow in the base64
decoding which allows a remote attacker using a prepared remote
server to execute code for the user using curl.
The Kerberos authorization has a similar bug, but is not compiled
in on SUSE Linux.
This is tracked by the Mitre CVE ID CAN-2005-0490.
2) solution/workaround
None, please install the fixed packages.
3) special instructions and notes
If you are using a service that uses libcurl, please restart this
service.
This list potentially includes the PHP4 support of the Apache and
Apache2 web servers.
4) package location and checksums
Please 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 to install from the maintenance web.
x86 Platform:
SUSE Linux 9.2:
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/curl-7.12.0-2.2.i586.rpm
10bdaa686d6fbc08cbe4620c91e6f33b
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/curl-devel-7.12.0-2.2.i586.rpm
fcab29842a028c41dbf5910a6b24c0e2
SUSE Linux 9.1:
ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/curl-7.11.0-39.4.i586.rpm
285dc0e7bafa207c2ab5f1c3081e2cdc
ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/curl-devel-7.11.0-39.4.i586.rpm
f0d88e1e0c78a8db1ae9adce3607a18e
x86-64 Platform:
SUSE Linux 9.2:
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/curl-7.12.0-2.2.x86_64.rpm
724387fba668aaf1f8772f5e45320676
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/curl-devel-7.12.0-2.2.x86_64.rpm
0c53e24c16610908324f3f4bb51174bd
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/curl-7.12.0-2.2.src.rpm
fb2533e28b02a5f2bdfe001e6c3c3d0a
SUSE Linux 9.1:
ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/curl-7.11.0-39.4.x86_64.rpm
08ae9314b886b1e51b422943aa42d210
ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/curl-devel-7.11.0-39.4.x86_64.rpm
44ca3527474d574bfca573efe78cd259
source rpm(s):
ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/curl-7.11.0-39.4.src.rpm
f8b455755a9da06399cfbe10edcf2b9f
______________________________________________________________________________
5) Pending vulnerabilities in SUSE Distributions and Workarounds:
See 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
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
announcement. Since the announcement containing the checksums is
cryptographically signed (usually using the key security@suse.de),
the checksums show proof of the authenticity of the package.
We disrecommend to subscribe to security lists which cause the
email 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
filename of the rpm package that you have downloaded. Of course,
package authenticity verification can only target an un-installed rpm
package file.
Prerequisites:
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 "build@suse.de" 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 ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de .
- SUSE runs two security mailing lists to which any interested party may
subscribe:
suse-security@suse.com
- general/linux/SUSE security discussion.
All SUSE security announcements are sent to this list.
To subscribe, send an email 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 email to
.
For general information or the frequently asked questions (faq)
send mail to:
or
respectively.
=====================================================================
SUSE's security contact is or .
@suse.de>.
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.
infamous41md@hotpop.com reported a vulnerability in libcurl, the
HTTP/FTP retrieval library. This library is used by lots of programs,
including YaST2 and PHP4.