-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: bind
Announcement ID: SUSE-SA:2009:005
Date: Thu, 22 Jan 2009 12:00:00 +0000
Affected Products: openSUSE 10.3
openSUSE 11.0
openSUSE 11.1
SUSE SLES 9
Novell Linux Desktop 9
Open Enterprise Server
Novell Linux POS 9
SLE SDK 10 SP2
SUSE Linux Enterprise Desktop 10 SP2
SUSE Linux Enterprise 10 SP2 DEBUGINFO
SUSE Linux Enterprise Server 10 SP2
Vulnerability Type: information disclosure
Severity (1-10): 7
SUSE Default Package: no
Cross-References: CVE-2009-0025
Content of This Advisory:
1) Security Vulnerability Resolved:
bind does not completely verify the OpenSSL certification chain
Problem Description
2) Solution or Work-Around
3) Special Instructions and Notes
4) Package Location and Checksums
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
none
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
The DNS daemon bind is used to resolve and lookup addresses on the inter-
net.
Some month ago a vulnerability in the DNS protocol and its numbers was
published that allowed easy spoofing of DNS entries. The only way to pro-
tect against spoofing is to use DNSSEC.
Unfortunately the bind code that verifys the certification chain of a DNS-
SEC zone transfer does not properly check the return value of function
DSA_do_verify(). This allows the spoofing of records signed with DSA or
NSEC3DSA.
2) Solution or Work-Around
none
3) Special Instructions and Notes
Please restart bind.
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.1:
openSUSE 11.0:
openSUSE 10.3:
x86-64 Platform:
openSUSE 11.1:
openSUSE 11.0:
openSUSE 10.3:
Sources:
openSUSE 11.1:
openSUSE 11.0:
openSUSE 10.3:
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
Open Enterprise Server
https://login.microfocus.com/nidp/app/login;keywords=3c0305962976100c07f4b568bf3ed2f1
Novell Linux POS 9
https://login.microfocus.com/nidp/app/login;keywords=3c0305962976100c07f4b568bf3ed2f1
Novell Linux Desktop 9
https://login.microfocus.com/nidp/app/login;keywords=3c0305962976100c07f4b568bf3ed2f1
SUSE SLES 9
https://login.microfocus.com/nidp/app/login;keywords=3c0305962976100c07f4b568bf3ed2f1
SUSE Linux Enterprise Server 10 SP2
https://login.microfocus.com/nidp/app/login;keywords=93598a8dd9d9622b980c3c2d7fdfcc61
SLE SDK 10 SP2
https://login.microfocus.com/nidp/app/login;keywords=93598a8dd9d9622b980c3c2d7fdfcc61
SUSE Linux Enterprise 10 SP2 DEBUGINFO
https://login.microfocus.com/nidp/app/login;keywords=93598a8dd9d9622b980c3c2d7fdfcc61
SUSE Linux Enterprise Desktop 10 SP2
https://login.microfocus.com/nidp/app/login;keywords=93598a8dd9d9622b980c3c2d7fdfcc61
______________________________________________________________________________
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
none
______________________________________________________________________________
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.
====================================================================
