-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: heimdal
Announcement ID: SUSE-SA:2005:040
Date: Wed, 06 Jul 2005 14:00:00 +0000
Affected Products: 8.2, 9.0, 9.1, 9.2
SUSE Linux Desktop 1.0
SUSE Linux Enterprise Server 8, 9
Novell Linux Desktop 9
Vulnerability Type: remote code execution
Severity (1-10): 9
SUSE Default Package: yes
Cross-References: CAN-2005-2040
Content of This Advisory:
1) Security Vulnerability Resolved:
heimdal telnetd remote buffer overflow
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
A remote buffer overflow has been fixed in the heimdal / kerberos
telnetd daemon which could lead to a remote user executing code as
root by overflowing a buffer.
This attack requires the use of the kerberized telnetd of the heimdal
suite, which is not used by default on SUSE systems.
This is tracked by the Mitre CVE ID CAN-2005-2040.
2) Solution or Work-Around
Please install the updated packages.
3) Special Instructions and Notes
Since the heimdal telnetd is usually started from inetd/xinetd,
no action is necessary.
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.
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web.
x86 Platform:
SUSE Linux 9.2:
3c58f2d19431fec5e398dac27df1f4d4
SUSE Linux 9.1:
d96212ff5cfae6790f33fd5fd2fbaf0e
source rpm(s):
e5b9e2eede280ee45908e7760119c00a
SUSE Linux 9.0:
810f6b76593cb4188a6f05da62edb983
source rpm(s):
05f4ce0b1bf5a8a277d72206723f5e66
SUSE Linux 8.2:
8d49e11b757755d4b59c0a2ec922ebb4
source rpm(s):
35ed1cbb68084f390d58009382c88712
x86-64 Platform:
SUSE Linux 9.2:
26fd8fbf592fc8b3f92afff2c2443a1f
source rpm(s):
34aed06065553bd7b2c20c24c7bbe66b
SUSE Linux 9.1:
628db7ea5c88db6ee84b7d90794e92a3
source rpm(s):
8c0bd4f6ccee1a87725262d37894b2a2
SUSE Linux 9.0:
0fc2978b91c3eee2397fc6c3ae811849
source rpm(s):
ad57d43e4b8d02705fd1e1861bfa56ab
______________________________________________________________________________
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:
suse-security@suse.com
- 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
.
For general information or the frequently asked questions (FAQ),
send mail to or
.
==================================================================== SUSE's security contact is or .
The public key is listed below.
====================================================================
