SuSE Security Announcement: openssl (SuSE-SA:2002:027)
-----BEGIN PGP SIGNED MESSAGE-----
______________________________________________________________________________
SuSE Security Announcement
Package: openssl
Announcement-ID: SuSE-SA:2002:027
Date: Tuesday, Jul 30th 2002 19:00 MEST
Affected products: 7.0, 7.1, 7.2, 7.3, 8.0
SuSE Linux Database Server,
SuSE eMail Server 3.1,
SuSE Linux Enterprise Server,
SuSE Linux Firewall on CD,
SuSE Linux Connectivity Server
SuSE Linux Office Server
Vulnerability Type: remote command execution
Severity (1-10): 8
SuSE default package: yes
Cross References: CAN-2002-0656, CAN-2002-0657, CAN-2002-0655,
CERT Advisory CA-2002-23
Content of this advisory:
1) security vulnerability resolved: openssl
problem description, discussion, solution and upgrade information
2) pending vulnerabilities, solutions, workarounds
3) standard appendix (further information)
______________________________________________________________________________
1) problem description, brief discussion, solution, upgrade information
The openssl package provides encryption functions and is used by many
applications on SuSE products.
Several buffer overflows have been discovered in the OpenSSL library
affecting the SSL implementation, as well as a signedness issue
in the ASN.1 decoding routines.
In the SSL library, various blobs of data passed from the client to
the server or vice versa were being copied to local buffers without
checking their size. At least one overflow in the SSLv2 server code can
be exploited by an attacker to gain access to the account under which
the SSL enabled service is running. The other overflows happen in the
SSL client code.
The impact of this bug depends on the service using SSL. When attacking
the Apache HTTP server with mod_ssl enabled, the perpetrator could gain
access to the account "wwwrun". Attacking other services, such as the
OpenLDAP slapd server, could even give the attacker access to the system's
root account.
Temporary workarounds for affected services include to disable the ssl
functionality where this is possible. For ssl-enabled webservers, it is
possible to temporarily disable SSLv2: Edit /etc/httpd/httpd.conf and
add the following line to the mod_ssl configuration group:
SSLProtocols all -SSLv2
This should be considered a temporary workaround only.
Since the SSL client implementation is affected as well, and due to the
potential impact of the ASN.1 signedness issues, we recommend that users
who do not run SSL enabled services upgrade their openssl package as well.
By consequence, we recommend all users to update their openssl package.
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.
SPECIAL INSTALL INSTRUCTIONS:
==============================
After performing the package update, all services using the openssl
libraries must be restarted for the update to become effective.
This can be done by rebooting the server or by individually restarting
the services in question manually. To find out which services use the
openssl libraries, use the command
fuser -v /usr/lib/libssl.so* /usr/lib/libcrypto.so*
The ASN1 parser vulnerability was discovered by Adi Stav and James Yonan
independently.
We would like to express our gratitude to the openssl team for
their work on the package and the fix for the vulnerability.
Intel i386 Platform:
SuSE-8.0:
ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec1/openssl-0.9.6c-78.i386.rpm
d68e8d7b95c8e08a26e8c43f8402dd9e
ftp://ftp.suse.com/pub/suse/i386/update/8.0/d3/openssl-devel-0.9.6c-78.i386.rpm
585843303f70fd248d7246255df67b04
ftp://ftp.suse.com/pub/suse/i386/update/8.0/doc4/openssl-doc-0.9.6c-78.i386.rpm
26a7ccff8ed167f6b75e8fe3fa8dd9f6
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/openssl-0.9.6c-78.src.rpm
f79da5c72786b565d3c974bc3c99fd96
SuSE-7.3:
ftp://ftp.suse.com/pub/suse/i386/update/7.3/sec1/openssl-0.9.6b-147.i386.rpm
d561da0a81b4c2672489af60c5dd8370
ftp://ftp.suse.com/pub/suse/i386/update/7.3/d2/openssl-devel-0.9.6b-147.i386.rpm
9a1bab09eeb257ac3431b3f59c7b6505
ftp://ftp.suse.com/pub/suse/i386/update/7.3/doc3/openssl-doc-0.9.6b-147.i386.rpm
f7c835278bec7df2efd630ba3c3c813f
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/openssl-0.9.6b-147.src.rpm
2dc2b9e91159b9f31becb9e60b089216
SuSE-7.2:
ftp://ftp.suse.com/pub/suse/i386/update/7.2/sec1/openssl-0.9.6a-63.i386.rpm
1e4e8c964ad7a199c79e01aab3df2f6f
ftp://ftp.suse.com/pub/suse/i386/update/7.2/d2/openssl-devel-0.9.6a-63.i386.rpm
e8e751d8c712956a57285fb85a14c390
ftp://ftp.suse.com/pub/suse/i386/update/7.2/doc3/openssl-doc-0.9.6a-63.i386.rpm
70ac1f005f8480a25b7ee5ef94e61582
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/openssl-0.9.6a-63.src.rpm
da7631d06555e889fd21b36b521488c1
SuSE-7.1:
ftp://ftp.suse.com/pub/suse/i386/update/7.1/sec1/openssl-0.9.6a-63.i386.rpm
4d77c7121cc5e917ef1e2d3a6cfa3e02
ftp://ftp.suse.com/pub/suse/i386/update/7.1/d2/openssl-devel-0.9.6a-63.i386.rpm
ab1e29c72446bf452ec35ba033aa0411
ftp://ftp.suse.com/pub/suse/i386/update/7.1/doc3/openssl-doc-0.9.6a-63.i386.rpm
0c1715237824236ce88011e9d63b16c0
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/openssl-0.9.6a-63.src.rpm
4300e98769f3e4743524b84c5d917148
SuSE-7.0:
ftp://ftp.suse.de/pub/suse/i386/update/7.0/sec1/openssl-0.9.5a-59.i386.rpm
609999f72998db65d514619271058c97
source rpm(s):
ftp://ftp.suse.de/pub/suse/i386/update/7.0/zq1/openssl-0.9.5a-59.src.rpm
313bc5e55757dc36414d3962306fa1b8
Sparc Platform:
The packages for the Sparc platform are being built by the time of the
writing of this announcement and will be published without any delay.
AXP Alpha Platform:
The packages for the Alpha platform are being built by the time of the
writing of this announcement and will be published without any delay.
PPC Power PC Platform:
SuSE-7.3:
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/sec1/openssl-0.9.6b-136.ppc.rpm
13c3473cea153733d903c7bc787f2570
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/d2/openssl-devel-0.9.6b-136.ppc.rpm
9d7dc120b55d29df6cb94c0930dfda1c
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/doc3/openssl-doc-0.9.6b-136.ppc.rpm
29f3db701df227c5f06de28b681c49dc
source rpm(s):
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/openssl-0.9.6b-136.src.rpm
deedc21663128548d830bf9c24c70add
SuSE-7.1:
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/sec1/openssl-0.9.6a-23.ppc.rpm
c7342fc2aced5e38c4cea73bc9012715
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/d2/openssl-devel-0.9.6a-23.ppc.rpm
ea0bc83b56fc373734aed4314a52babb
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/doc3/openssl-doc-0.9.6a-23.ppc.rpm
33db969774904ce36a4d79a69af4c85a
source rpm(s):
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/openssl-0.9.6a-23.src.rpm
f0c1fc2a70e453731d19378f8f1ba351
SuSE-7.0:
ftp://ftp.suse.de/pub/suse/ppc/update/7.0/sec1/openssl-0.9.5a-8.ppc.rpm
0b839d3c13e0250eeb16728ba2ed2354
source rpm(s):
ftp://ftp.suse.de/pub/suse/ppc/update/7.0/zq1/openssl-0.9.5a-8.src.rpm
e2837b523654fc7ac73c1b94e2627c60
______________________________________________________________________________
2) Pending vulnerabilities in SuSE Distributions and Workarounds:
- chfn/util-linux
Linux distributors have published security announcements about password
locking race conditions that lead to a local root vulnerability.
SuSE products are not affected by this weakness because we use the
user/group management utilities from the shadow package. These utilities
are not affected.
- mod_ssl
An off-by-one buffer overflow in the mod_ssl apache module is subject to
an upcoming SuSE Security announcement, following this announcement.
The upcoming announcement also treats a temporary file handling problem
that has been discovered by Markus Meissner and Sebastian Krahmer,
SuSE Security.
- libpng
libpng is a library that provides functions for applications to handle
PNG image files (Portable Network Graphics). An overflow vulnerability
has been found in the libpng library that may make it possible for an
attacker to run arbitrary code or to crash an application that uses
the libpng library if the application in question opens a png image file.
We are in the process of fixing this vulnerability.
- wwwoffle (World Wide Web Offline Explorer)
wwwoffle fails to handle negative Content-Length values correctly.
It is believed that an attacker can exploit this bug to gain remote
access to the system running wwwoffle.
We are working on update packages against this problem.
- mod_php4-4.2*
Security vulnerabilities have been found in php versions 4.2.0 and 4.2.1.
SuSE systems are not affected because these systems use older versions
of the php package.
- The SuSE Linux 6.4 distribution has been announced to be discontinued
in June. We have now moved the update directories for all architectures
to the discontinued directory on our ftp server to indicate that no more
updates will be made for this distribution.
______________________________________________________________________________
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:
1) md5sums as provided in the (cryptographically signed) announcement.
2) using the internal gpg signatures of the rpm package.
1) execute the command
md5sum
Am Die, 2002-07-30 um 19.27 schrieb Roman Drahtmueller:
fuser -v /usr/lib/libssl.so* /usr/lib/libcrypto.so*
I have a totally modified SuSE 7.0 Installation and I was wondering if I really have to update this older system, because this might cause a really major headache to me. (of cause all other newer-not-totally-patched-systems are right now updated) fuser -v etc. shows no program whichs is really using the openssl lib. Otherwise my cyrus imapd and my apache with ssl support is currently running (mod_ssl). lsof|grep ssl shows some other open lib files, but no the /usr/lib/libssl.so or /usr/lib/libcrypto.so: httpd 25447 root mem REG 8,5 934084 134240 /usr/lib/apache/libssl.so sslwrap 31654 cyrus txt REG 8,5 760575 137723 /usr/sbin/sslwrap [...] Should I buy some aspirin?!? ;-)
Openssh uses openssl. Is openssh vulnerable to any of the openssl exploits?
On Tue, Jul 30, 2002 at 09:58:43PM +0100, Graham Murray wrote:
Openssh uses openssl. Is openssh vulnerable to any of the openssl exploits?
Potentially, yes. It may be possible to trigger the ASN.1 signedness bug when decoding RSA keys during/after RSA authentication. The other bugs, no, because OpenSSH doesn't use SSL. Olaf -- Olaf Kirch | Anyone who has had to work with X.509 has probably okir@suse.de | experienced what can best be described as ---------------+ ISO water torture. -- Peter Gutmann
Olaf Kirch wrote:
On Tue, Jul 30, 2002 at 09:58:43PM +0100, Graham Murray wrote:
Openssh uses openssl. Is openssh vulnerable to any of the openssl exploits?
Potentially, yes. It may be possible to trigger the ASN.1 signedness bug when decoding RSA keys during/after RSA authentication. The other bugs, no, because OpenSSH doesn't use SSL.
AFAIK by now, this is only "exploitable", if there are RSA2-Keys in your authorized_keys, it might even only be exploitable on BSDs (but I'm not very sure about that) (According to Markus Friedl from OpenSSH). But there's no possibility of an anonymous exploit. Use DSA-Keys and you should be safe. I probably would have lost this mornings breakfast if SSH would've been vulnerable *again*. Ralph
Hi, does anyone know if web browsers like Opera, Netscape etc. are vulnerable, too? What kind of ssl implementation do they use, openssl or. sth else? Thx! Best regards, Frank -- Dipl.-Inform. Frank Steiner mailto:fst@informatik.uni-kiel.de Lehrstuhl f. Programmiersprachen mailto:fsteiner@web.de CAU Kiel, Olshausenstraße 40 Phone: +49 431 880-7265, Fax: -7613 D-24098 Kiel, Germany http://www.informatik.uni-kiel.de/~fst/
On Wed, Jul 31, 2002 at 11:08:13AM +0200, Frank Steiner wrote:
Hi,
does anyone know if web browsers like Opera, Netscape etc. are vulnerable, too? What kind of ssl implementation do they use, openssl or. sth else?
Communicator uses RSA's BSAFE by default. Mozilla uses some home-brew stuff; Opera I can't say. rpm -qR should tell you whether they need libcrypto and/or libssl. Olaf -- Olaf Kirch | Anyone who has had to work with X.509 has probably okir@suse.de | experienced what can best be described as ---------------+ ISO water torture. -- Peter Gutmann
Olaf Kirch wrote:
On Wed, Jul 31, 2002 at 11:08:13AM +0200, Frank Steiner wrote:
Hi,
does anyone know if web browsers like Opera, Netscape etc. are vulnerable, too? What kind of ssl implementation do they use, openssl or. sth else?
Communicator uses RSA's BSAFE by default. Mozilla uses some home-brew stuff; Opera I can't say. rpm -qR should tell you whether they need libcrypto and/or libssl.
Thanks for the hint, it seems Opera uses some internal stuff, so I will have to ask them... Thx! Best regards, Frank -- Dipl.-Inform. Frank Steiner mailto:fst@informatik.uni-kiel.de Lehrstuhl f. Programmiersprachen mailto:fsteiner@web.de CAU Kiel, Olshausenstraße 40 Phone: +49 431 880-7265, Fax: -7613 D-24098 Kiel, Germany http://www.informatik.uni-kiel.de/~fst/
Hi! On Tue, 30 Jul 2002, Roman Drahtmueller wrote:
SPECIAL INSTALL INSTRUCTIONS: ============================== After performing the package update, all services using the openssl libraries must be restarted for the update to become effective. This can be done by rebooting the server or by individually restarting the services in question manually. To find out which services use the openssl libraries, use the command
fuser -v /usr/lib/libssl.so* /usr/lib/libcrypto.so*
I just noticed that this line will only show correct results *before* the upgrade - which makes sense: the old libs have been replaced during the upgrade, but running processes still use the *old* (deleted) libs - so the fuser command can't report them. Perhaps the next advisory should mention this problem... As a workaround, after the upgrade one can use something like: lsof | grep "/usr/lib/libssl.so*\|/usr/lib/libcrypto.so*" which results in something like: pine 14262 mk mem DEL 3,7 192668 /usr/lib/libssl.so.0.9.6-RPMDELETE ... Cheers, Martin
Martin Köhling wrote:
As a workaround, after the upgrade one can use something like:
lsof | grep "/usr/lib/libssl.so*\|/usr/lib/libcrypto.so*"
which results in something like:
pine 14262 mk mem DEL 3,7 192668 /usr/lib/libssl.so.0.9.6-RPMDELETE
or: lsof | grep RPMDELETE :)
Am Wed, Jul 31, 2002 at 11:41:48AM +0200, schrieb Martin Köhling:
On Tue, 30 Jul 2002, Roman Drahtmueller wrote:
fuser -v /usr/lib/libssl.so* /usr/lib/libcrypto.so*
I just noticed that this line will only show correct results *before* the upgrade - which makes sense: the old libs have been replaced during the upgrade, but running processes still use the *old* (deleted) libs - so the fuser command can't report them.
Perhaps the next advisory should mention this problem...
I'd like to emphasize this. Otherwise it will happen to many users what happened to me: the cited fuser command didn't show anything, so I thought I was fine. But today, after reading your mail, a lsof | grep RPMDELETE made me discover that httpd, sslwrap (and with that: sendmail and pop3), fetchmail and sshd, i.e. all (!) services offered by my server still used the old libraries. I corrected this by killing (-15) xinetd, restarting xinetd and sshd, and gracefully restarting httpd (kill -10). So please say in an additional advisory what is necessary. Thanks and bye, Hatto v. Hatzfeld
Roman Drahtmueller wrote:
Content of this advisory: 1) security vulnerability resolved: openssl problem description, discussion, solution and upgrade information
Just one question: We still use SuSE EmailServer-2 which uses sslwrap to enable imaps and pop3s on the server. sslwrap doesn't seem to be dynamically linked to OpenSSL: ldd /usr/sbin/sslwrap libc.so.6 => /lib/libc.so.6 (0x40018000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) Is this a statically linked binary or does sslwrap use its own SSL-Code, meaning that it's not vulnerable? Ralph
On Wed, Jul 31, 2002 at 01:59:09PM +0200, Ralph Angenendt wrote:
Roman Drahtmueller wrote:
Content of this advisory: 1) security vulnerability resolved: openssl problem description, discussion, solution and upgrade information
Just one question: We still use SuSE EmailServer-2 which uses sslwrap to enable imaps and pop3s on the server. sslwrap doesn't seem to be dynamically linked to OpenSSL:
ldd /usr/sbin/sslwrap libc.so.6 => /lib/libc.so.6 (0x40018000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
Is this a statically linked binary or does sslwrap use its own SSL-Code, meaning that it's not vulnerable?
sslwrap uses OpenSSL. In fact, if there is no other packet with the same name around, sslwrap is an old software based on the OpenSSL "s_server" functionality. (I don't know when it forked off, it may even be that the library was named SSLeay at that time). It should therefore be considered to be vulnerable. Best regards, Lutz -- Lutz Jaenicke Lutz.Jaenicke@aet.TU-Cottbus.DE http://www.aet.TU-Cottbus.DE/personen/jaenicke/ BTU Cottbus, Allgemeine Elektrotechnik Universitaetsplatz 3-4, D-03044 Cottbus
participants (10)
-
Frank Steiner -
Graham Murray -
Hatto von Hatzfeld -
Lutz Jaenicke -
Martin Köhling -
Olaf Kirch -
Ralph Angenendt -
Roman Drahtmueller -
Sven 'Darkman' Michels -
Torge Szczepanek