SUSE Security Announcement
Package: openssl
Announcement-ID: SuSE-SA:2004:007
Date: Wednesday, Mar 17th 2004 13:30 MEST
Affected products: 8.0, 8.1, 8.2, 9.0 SuSE Linux Database Server,
SuSE eMail Server III, 3.1 SuSE Linux Enterprise Server 7, 8 SuSE
Linux Firewall on CD/Admin host SuSE Linux Connectivity Server SuSE
Linux Office Server
Vulnerability Type: remote denial-of-service
Severity (1-10): 4
SUSE default package: yes
Cross References: CAN-2004-0079 CAN-2004-0112
Content of this advisory:
- security vulnerability resolved:
- null pointer assignment due to handshake
- crash with Kerberos cipher-suite support problem description,
discussion, solution and upgrade information
- pending vulnerabilities, solutions, workarounds:
- xf86_glx/xmodules/xloader
- gnome-session
- pwlib
- libxml2
- mod_python
- mozilla
- kernel
- mailman
- metamail
- sysstat
- standard appendix (further information)
1) problem description, brief discussion, solution, upgrade
information
OpenSSL is an implementation of the Secure Socket Layer (SSL
v2/3) and Transport Layer Security (TLS v1) protocol. The NISCC
informed us about to failure conditions in openssl that can be
triggered to crash applications that use the openssl library.
The first bug occurs during SSL/TLS handshake in the function
do_change_cipher_spec() due to a NULL pointer assignment. The
second bug affects openssl version 0.9.7* only with Kerberos
cipher-suite enabled and can be triggered during SSL/TLS handshake
too.
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.
There is not other solution known to this problem then updating
to the current version from our FTP servers.
To make this update effective, restart all servers using openssl
please
Intel i386 Platform:
SuSE-9.0:
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/openssl-0.9.7b-133.i586.rpm
31ec7dd8d5e119ebc0c63b287e4ad3c7
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/openssl-devel-0.9.7b-133.i586.rpm
952ad40732b95ca7fdd8ba00a94ce99b
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/openssl-0.9.7b-133.i586.patch.rpm
71d9522ca81e5cec829266f5fd9efb6d
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/openssl-devel-0.9.7b-133.i586.patch.rpm
40d2d30ff2f2629d02e6e54472b6aca0
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/openssl-0.9.7b-133.src.rpm
3bb291108685b06ac25533014ede039e
SuSE-8.2:
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-0.9.6i-21.i586.rpm
21d83138d00c84b0febc2428f1e5ceac
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-devel-0.9.6i-21.i586.rpm
421bf9717ff3c7facc8a6ee51438e82c
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-0.9.6i-21.i586.patch.rpm
0457b801931f1f6857e3358c4b5a9151
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/openssl-devel-0.9.6i-21.i586.patch.rpm
4d8561d55cde4d31c840ebd7d10901e1
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/openssl-0.9.6i-21.src.rpm
4a55e2eae1fd8ebcc086fa612d9af95b
SuSE-8.1:
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-0.9.6g-114.i586.rpm
53c938f88ed6a5d2ad12120c65ea880f
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-devel-0.9.6g-114.i586.rpm
bd6ff0ccaf12c1ce9107accf5f4372b6
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-0.9.6g-114.i586.patch.rpm
7782f761018a0b4fb95c955f7c782b6d
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/openssl-devel-0.9.6g-114.i586.patch.rpm
51df3d52a98175cbe6338cb963140a59
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/openssl-0.9.6g-114.src.rpm
da2f5a9f62126ad0e1659a6f4f78878c
SuSE-8.0:
ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec1/openssl-0.9.6c-87.i386.rpm
f40a9640a6acc1ba9bbd3c2669ecba9d
ftp://ftp.suse.com/pub/suse/i386/update/8.0/d3/openssl-devel-0.9.6c-87.i386.rpm
d19730d5050a0f0fd5cafb348c0c0896
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec1/openssl-0.9.6c-87.i386.patch.rpm
e81f85173f6108f1e1ce312540fcff48
ftp://ftp.suse.com/pub/suse/i386/update/8.0/d3/openssl-devel-0.9.6c-87.i386.patch.rpm
9fbb35bdf838262ccb56b4c3924c3a08
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/openssl-0.9.6c-87.src.rpm
0b09e243d99922087ace4052f330f493
2) Pending vulnerabilities in SUSE Distributions and
Workarounds:
- xf86_glx/xmodules/xloader
The GLX and DRI code of the Xserver did not verify the “screen”
parameter in several functions. This failure leads to a
denial-ofservice condition and probably to arbitrary code execution
as root. New packages are available on our FTP servers. - gnome-session
This updates solves a problem with the initialization of the
LD_LIBRARY_PATH while starting GNOME by using /usr/X11R6/bin/gnome.
This bug can lead to local privilege escalation. New packages are
available on our FTP servers. - pwlib
This update addresses several security vulnerabilities that may be
exploited remotely via applications that link with pwlib, like
GnomeMeeting or alike. New packages are available on our FTP
servers. - libxml2
A buffer overflow in the URI parsing code is fixed. This bug can
lead to remote access to a system using libxml2. New packages are
available on our FTP servers. - mod_python
A remote denial-of-service attack can be triggered against the
Apache web server by sending a specific query string that is
processed by mod_python. New packages are available on our FTP
servers. - mozilla
A buffer overflow in the S/MIME code of mozilla has been fixed
which could allow remote attackers to execute arbitrary commands as
the user running mozilla. Additionally a flaw in cookie handling
(CAN-2003-0592) and a cross-site-scripting bug was fixed. In some
cases (as with the mozilla package) the complexity of the issue
does not allow to add patches any more. By consequence, security
related issues in mozilla cannot be addressed. As a service to our
user community, we provide packages of newer mozilla versions at
ftp://ftp.suse.com/pub/projects/mozilla/.
These packages have been verified to run fine; they are not located
in the update directory of the distribution in question because we
cannot make any claims about the compatibility with the other
packages in the product - kernel
A new kernel release was made available. This update fixes some
minor local denial-of-service attacks. Additionally, the 8.2
versions also includes a missing patch from SuSE-SA:2004:005. - mailman
A remote denial-of-service attack can be triggered in mailman 2.0.x
(CAN-2003-0991). New packages will be available soon. - metamail
This update fixes two buffer overflows and two format string bugs
that can be exploited remotely in conjunction with other tools to
gain access to a system with the privileges of the user running New
packages will be available soon. - sysstat
Two cases of insecure temporary file handling were found. The
packages are currently being tested and will be available
soon.
3) 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:- md5sums as provided in the (cryptographically signed)
announcement. - using the internal gpg signatures of the rpm package.
- execute the command md5sum <name-of-the-file.rpm> 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 [email protected]), 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. - rpm package signatures provide an easy way to verify the
authenticity of an rpm package. Use the command rpm -v –checksig
<file.rpm> to verify the signature of the package, where
<file.rpm> 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:- gpg is installed
- 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 “[email protected]”
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
.
- md5sums as provided in the (cryptographically signed)
- SUSE runs two security mailing lists to which any interested
party may subscribe: - general/linux/SUSE security discussion. All SUSE security
announcements are sent to this list. To subscribe, send an email to - 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:
<[email protected]>
or
<[email protected]>
respectively.
SUSE’s security contact is <[email protected]> or
<[email protected]>.
The <[email protected]> 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.
Type | Bits/KeyID | Date | User ID |
pub | 2048R/3D25D3D9 | 1999-03-06 | SuSE Security Team <[email protected]> |
pub | 1024D/9C800ACA | 2000-10-19 | SuSE Package Signing Key <[email protected]> |