-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: krb5
Announcement ID: SUSE-SA:2007:004
Date: Wed, 10 Jan 2007 12:00:00 +0000
Affected Products: openSUSE 10.2
SUSE LINUX 10.1
SUSE LINUX 10.0
SUSE LINUX 9.3
SUSE SLED 10
SUSE SLES 10
Vulnerability Type: remote denial of service
Severity (1-10): 6
SUSE Default Package: yes
Cross-References: CVE-2006-6143, CVE-2006-6144
Content of This Advisory:
1) Security Vulnerability Resolved:
krb5 security problems
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
Various bugs in the Kerberos5 libraries and tools were fixed which
could be used by remote attackers to crash and potentially execute
code in kadmind.
- CVE-2006-6144 / MITKRB5-SA-2006-002: the RPC library could call an
uninitialized function pointer, which created a security
vulnerability for kadmind.
- CVE-2006-6143 / MITKRB5-SA-2006-003: the GSS-API mechglue layer
could fail to initialize some output pointers, causing callers to
attempt to free uninitialized pointers. This caused a security
vulnerability in kadmind.
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
None.
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:
4ca25054bbab5904788c59770244f7db
1255b216e9ccd859dd48d408ff3c47fe
SUSE LINUX 10.1:
bb069e7b8a87d1b37d295845d42f01b7
216fbc03ebf686e4fb0e97ea9af37663
SUSE LINUX 10.0:
b64ae4d898a21a45215f910d79e25846
41cfd49f686df98c58e952ac35f884f4
SUSE LINUX 9.3:
8217967cf7b1cbe2f110b62d6587f1ed
e53acbadff99aef651c0bffe9b635cc4
Power PC Platform:
openSUSE 10.2:
926d4584a5b99b3e2c4b6e2d7c82f207
147cbf384e74834f8bd3ae85b6558801
SUSE LINUX 10.1:
0f64972c3effc2e8b8d6c60e6cc83ee2
b05b1f047f45cb3dae619803c35b2064
SUSE LINUX 10.0:
8b848a4cdb5eeca47145665009ee6999
788cea6376b8d0d4fbb7ae6841b1121e
x86-64 Platform:
openSUSE 10.2:
5048fe45c961d2a101c359beee6dfd90
aab68447731fe22bbf3e7133411658eb
76d07392dbfa6ce64afb748724ffc383
SUSE LINUX 10.1:
4f28bc902dd81ba3154c8ab502dd6be6
e8cb3fd1f9040c3c162e84f76e490578
b9f3d11d3ee957b0f228c5276a84005b
SUSE LINUX 10.0:
dedeffa46109d7339ec71122122589db
4bce2876d9c1b883207e03dc34513eb2
1ef250e5e23a298349f28b2423e3a8f2
SUSE LINUX 9.3:
82e4c415098edcaca10ab626cb304bed
e2cdaaf22c5ecf51274c6d87731cbd7f
861fb648231993f96b6c9bb789c6fba2
Sources:
openSUSE 10.2:
49e80a10bedad6caf6584c91262bacb4
SUSE LINUX 10.1:
8a116157fed412cb74c84157391a25e1
SUSE LINUX 10.0:
de6594481cd93860c81a66befa90179e
SUSE LINUX 9.3:
8e24ef8f705e1c00fe5f2158198e0ed1
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
SUSE SLES 10
http://support.novell.com/techcenter/psdb/719d380dfd2862678d739af24aefaf29.html
SUSE SLED 10
http://support.novell.com/techcenter/psdb/719d380dfd2862678d739af24aefaf29.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.
====================================================================
