-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: bind
Announcement ID: SUSE-SA:2007:014
Date: Tue, 30 Jan 2007 11:00:00 +0000
Affected Products: SUSE LINUX 9.3
SUSE LINUX 10.0
SUSE LINUX 10.1
openSUSE 10.2
UnitedLinux 1.0
SuSE Linux Enterprise Server 8
SuSE Linux Openexchange Server 4
SuSE Linux Standard Server 8
SuSE Linux School Server
SUSE LINUX Retail Solution 8
SUSE SLES 9
Novell Linux Desktop 9
Open Enterprise Server
Novell Linux POS 9
SUSE SLED 10
SUSE SLES 10
Vulnerability Type: remote denial of service
Severity (1-10): 5
SUSE Default Package: no
Cross-References: CVE-2007-0493, CVE-2007-0494
Content of This Advisory:
1) Security Vulnerability Resolved:
remote denial of service problem in BIND
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
Two security problems were fixed in the ISC BIND nameserver
version 9.3.4, which are addressed by this advisory:
CVE-2007-0493: If recursion is enabled, a remote attacker can dereference
a freed fetch context causing the daemon to abort / crash.
CVE-2007-0494: By sending specific DNS query responses with multiple
RRSETS attackers could cause BIND to exit abnormally.
Updates for SUSE Linux Enterprise Server were released on Friday 26th of January,
updates for SUSE Linux and openSUSE were released on Monday 29th of January.
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 bind after the update.
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 10.2:
1cbff49e03831710c990961534db5ec1
bd6462a783b85946e8e3397fdd972e48
ff37774a0bf31c329e834b4ffa3275ed
SUSE LINUX 10.1:
5748e1f4000a2f778f0598b97ee3f41f
e88a84c84c7d23e2e5fd4184e040ea36
91758b51c5dce9ea1e6c807d0b5a5ec0
SUSE LINUX 10.0:
75b21dd87a6c02af3c129cdac1c914f0
e2d482990c6336041ecda4263130cbff
b0646b7097fd3221491f2afbe3f9ebbe
SUSE LINUX 9.3:
9f784583c4944a67f4a952220caefc23
e42f646c068f947c1d50a62bae1e21e4
244eb1e7ab236e4f5fb289569385c41d
Power PC Platform:
openSUSE 10.2:
196da83c1ee0bc0b836590ed4fec2d25
1f86c42742226e9a5bb7600fec5583ec
57697a572ef517d8906c6bf4e9d0a7a3
SUSE LINUX 10.1:
dba983ba548a847f1024246ff4bb3388
c15f6131a5484abdb03662e271d58eba
bb0ea32c59dcfa9a544b96d6e39ac83e
SUSE LINUX 10.0:
4c75aad7305260b263671fa1b5d3f90f
73c8917a37f96f9748394407d7f31706
534c2ff4a0a31d5fab474d720b290339
x86-64 Platform:
openSUSE 10.2:
ba6e1e48cee8fc94e047b0ffa927e405
ee297428f209bcb73f51599045b06d97
c04b66a303fc420a2682895716798758
2cf0460d5566d12b7cf82a30646d97e0
SUSE LINUX 10.1:
5b06fe8290edc659fd4e08b972ad8042
520983bb39f0ebf484054f5c848eb8ec
e0606262be2447a97700c31a259732b8
a3bb7fa67d39b821739d3993a0591729
SUSE LINUX 10.0:
04f58a6c8dc234adb99a93e379e0e932
1e4506d5cb2f72c8fa0e037a36f44fbf
ea0e2ad36c5031b57b8edb0a5d0f61d1
dc13d333deeb7a0f9980ffee7df26dae
SUSE LINUX 9.3:
5f684d89127ec370d6482f387f9fe53b
eafc69be579bf262055faf7784d76552
68dbc644298e95f321909f38edc1bc99
55f114b7938d9e822ffd4a37106f23d9
Sources:
openSUSE 10.2:
fa26ab535120777311837ffbcf2fb8b7
SUSE LINUX 10.1:
4047b6af5646920c8cffdb3c1891b090
SUSE LINUX 10.0:
e0a354000d30e1cd4c8d05cabf7bfff1
SUSE LINUX 9.3:
207a60f5455dcfc3c494ac00f9ec49fe
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
UnitedLinux 1.0
http://support.novell.com/techcenter/psdb/1906b69f138f410028362737dc020b6c.html
SuSE Linux Openexchange Server 4
http://support.novell.com/techcenter/psdb/1906b69f138f410028362737dc020b6c.html
SuSE Linux Enterprise Server 8
http://support.novell.com/techcenter/psdb/1906b69f138f410028362737dc020b6c.html
SuSE Linux Standard Server 8
http://support.novell.com/techcenter/psdb/1906b69f138f410028362737dc020b6c.html
SuSE Linux School Server
http://support.novell.com/techcenter/psdb/1906b69f138f410028362737dc020b6c.html
SUSE LINUX Retail Solution 8
http://support.novell.com/techcenter/psdb/1906b69f138f410028362737dc020b6c.html
Open Enterprise Server
http://support.novell.com/techcenter/psdb/ebd0655e8b4230a45daa0865dc0cd57a.html
Novell Linux POS 9
http://support.novell.com/techcenter/psdb/ebd0655e8b4230a45daa0865dc0cd57a.html
Novell Linux Desktop 9
http://support.novell.com/techcenter/psdb/ebd0655e8b4230a45daa0865dc0cd57a.html
SUSE SLES 10
http://support.novell.com/techcenter/psdb/ebd0655e8b4230a45daa0865dc0cd57a.html
SUSE SLED 10
http://support.novell.com/techcenter/psdb/ebd0655e8b4230a45daa0865dc0cd57a.html
SUSE SLES 9
http://support.novell.com/techcenter/psdb/ebd0655e8b4230a45daa0865dc0cd57a.html
______________________________________________________________________________
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.
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) Using the internal gpg signatures of the rpm package
2) MD5 checksums as provided in this announcement
1) 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.
2) If you need an alternative means of verification, use the md5sum
command to verify the authenticity of the packages. 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
SUSE security announcement. Because the announcement containing the
checksums is cryptographically signed (by security@suse.de), the
checksums show proof of the authenticity of the package if the
signature of the announcement is valid. Note that the md5 sums
published in the SUSE Security Announcements are valid for the
respective packages only. Newer versions of these packages cannot be
verified.
- 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
.
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 e-mail to
.
==================================================================== SUSE's security contact is or .
The public key is listed below.
====================================================================
