-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: openssl
Announcement ID: SUSE-SA:2010:020
Date: Tue, 06 Apr 2010 15:00:00 +0000
Affected Products: openSUSE 11.1
openSUSE 11.2
SUSE SLES 9
Open Enterprise Server
Novell Linux POS 9
SUSE Linux Enterprise Desktop 10 SP2
SUSE Linux Enterprise Desktop 10 SP3
SUSE Linux Enterprise Server 10 SP2
SUSE Linux Enterprise Server 10 SP3
SUSE Linux Enterprise Desktop 11
SUSE Linux Enterprise Server 11
SLE SDK 10 SP2
SLE SDK 10 SP3
SUSE Linux Enterprise Software Development Kit 11
SUSE Linux Enterprise 10 SP2 DEBUGINFO
SUSE Linux Enterprise 10 SP3 DEBUGINFO
SLE 11 DEBUGINFO
Vulnerability Type: remote denial of service, man in the middle attacks
CVSS v2 Base Score: 6.4 (AV:N/AC:L/Au:N/C:N/I:P/A:P)
SUSE Default Package: yes
Cross-References: CVE-2009-3245, CVE-2009-3555
Content of This Advisory:
1) Security Vulnerability Resolved:
openssl security update
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
The openSSL library was updated to add support for the new RFC5746
TLS renegotiation feature to address vulnerabilities tracked as
CVE-2009-3555, backported from openssl 0.9.8m.
The previous update (SUSE-SA:2009:057) completely disabled the unsafe
renegotiation.
This update will:
- automatically use the new secure renegotiation if present in both
server and client
- allow services to enable insecure renegotiation by setting flags
(default to off)
Using the secure renegotiation requires also fixed client cryptographic
libraries, for this we will also be releasing Mozilla NSS and GnuTLS
updates soon.
The openssl update also fixes a mishandling of OOM conditions in
bn_wexpand (CVE-2009-3245). Note that while some rating agencies
refer to this issue as easily exploitable for remote code execution
we consider it as both hard to exploit and still unproven to be
exploitable at all.
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
openssl after the update. (This will also happen with the next reboot
of the machine.)
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:
openSUSE 11.2:
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/i586/libopenssl-devel-0.9.8k-3.7.1.i586.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/i586/libopenssl0_9_8-0.9.8k-3.7.1.i586.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/i586/openssl-0.9.8k-3.7.1.i586.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/i586/openssl-doc-0.9.8k-3.7.1.i586.rpm
openSUSE 11.1:
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/i586/libopenssl-devel-0.9.8h-28.15.1.i586.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/i586/libopenssl0_9_8-0.9.8h-28.15.1.i586.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/i586/openssl-0.9.8h-28.15.1.i586.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/i586/openssl-doc-0.9.8h-28.15.1.i586.rpm
Platform Independent:
openSUSE 11.2:
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/noarch/openssl-certs-0.9.8h-28.2.1.noarch.rpm
openSUSE 11.1:
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/noarch/openssl-certs-0.9.8h-25.2.19.noarch.rpm
Power PC Platform:
openSUSE 11.1:
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/ppc/libopenssl-devel-0.9.8h-28.15.1.ppc.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/ppc/libopenssl0_9_8-0.9.8h-28.15.1.ppc.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/ppc/libopenssl0_9_8-64bit-0.9.8h-28.15.1.ppc.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/ppc/openssl-0.9.8h-28.15.1.ppc.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/ppc/openssl-doc-0.9.8h-28.15.1.ppc.rpm
x86-64 Platform:
openSUSE 11.2:
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/x86_64/libopenssl-devel-0.9.8k-3.7.1.x86_64.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/x86_64/libopenssl0_9_8-0.9.8k-3.7.1.x86_64.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/x86_64/libopenssl0_9_8-32bit-0.9.8k-3.7.1.x86_64.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/x86_64/openssl-0.9.8k-3.7.1.x86_64.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/x86_64/openssl-doc-0.9.8k-3.7.1.x86_64.rpm
openSUSE 11.1:
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/x86_64/libopenssl-devel-0.9.8h-28.15.1.x86_64.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/x86_64/libopenssl0_9_8-0.9.8h-28.15.1.x86_64.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/x86_64/libopenssl0_9_8-32bit-0.9.8h-28.15.1.x86_64.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/x86_64/openssl-0.9.8h-28.15.1.x86_64.rpm
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/x86_64/openssl-doc-0.9.8h-28.15.1.x86_64.rpm
Sources:
openSUSE 11.2:
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/src/openssl-certs-0.9.8h-28.2.1.src.rpm
openSUSE 11.1:
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/src/openssl-certs-0.9.8h-25.2.19.src.rpm
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
SUSE Linux Enterprise Server 11
https://login.microfocus.com/nidp/app/login
SUSE Linux Enterprise Desktop 11
https://login.microfocus.com/nidp/app/login
SUSE Linux Enterprise Software Development Kit 11
https://login.microfocus.com/nidp/app/login
Open Enterprise Server
https://login.microfocus.com/nidp/app/login
Novell Linux POS 9
https://login.microfocus.com/nidp/app/login
SUSE SLES 9
https://login.microfocus.com/nidp/app/login
SLE SDK 10 SP3
https://login.microfocus.com/nidp/app/login
SUSE Linux Enterprise Server 10 SP3
https://login.microfocus.com/nidp/app/login
SUSE Linux Enterprise Desktop 10 SP3
https://login.microfocus.com/nidp/app/login
SLE SDK 10 SP2
https://login.microfocus.com/nidp/app/login
SUSE Linux Enterprise Server 10 SP2
https://login.microfocus.com/nidp/app/login
SUSE Linux Enterprise Desktop 10 SP2
https://login.microfocus.com/nidp/app/login
______________________________________________________________________________
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.
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.
- SUSE runs two security mailing lists to which any interested party may
subscribe:
opensuse-security@opensuse.org
- General Linux and SUSE security discussion.
All SUSE security announcements are sent to this list.
To subscribe, send an e-mail to
.
opensuse-security-announce@opensuse.org
- SUSE's announce-only mailing list.
Only SUSE's security announcements are sent to this list.
To subscribe, send an e-mail to
.
==================================================================== SUSE's security contact is or .
The public key is listed below.
====================================================================
