-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: ethereal
Announcement ID: SUSE-SA:2006:065
Date: Tue, 14 Nov 2006 11:00:00 +0000
Affected Products: Novell Linux POS 9
Open Enterprise Server
SUSE LINUX 10.1
SUSE LINUX 10.0
SUSE LINUX 9.3
SuSE Linux Enterprise Server 8
SuSE Linux Openexchange Server 4
SUSE LINUX Retail Solution 8
SuSE Linux School Server
SuSE Linux Standard Server 8
SUSE SLED 10
SUSE SLES 10
SUSE SLES 9
UnitedLinux 1.0
Vulnerability Type: remote denial of service
Severity (1-10): 5
SUSE Default Package: no
Cross-References: CVE-2006-4574, CVE-2006-4805, CVE-2006-5468
CVE-2006-5469, CVE-2006-5740
Content of This Advisory:
1) Security Vulnerability Resolved:
several security problems in wireshark/ethereal
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 problems have been fixed in the network analyzer Ethereal (now called
Wireshark), most of them leading to crashes of the ethereal program.
CVE-2006-5740: An unspecified vulnerability in the LDAP dissector
could be used to crash Ethereal.
CVE-2006-4574: A single \0 byte heap overflow was fixed in the MIME multipart
dissector. Potential of exploitability is unknown, but considered low.
CVE-2006-4805: A denial of service problem in the XOT dissector can cause
it to take up huge amount of memory and crash ethereal.
CVE-2006-5469: The WBXML dissector could be used to crash ethereal.
CVE-2006-5468: A NULL pointer dereference in the HTTP dissector could
crash ethereal.
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:
SUSE LINUX 10.1:
6aecc0deb29a6339f1fa941c65844c6d
4c207d76c0f0ada418b790dadcff33f5
SUSE LINUX 10.0:
2f904b719bfbed232744856a4f9eca91
f6957aa0c03893d7fd47873999aaf5c1
SUSE LINUX 9.3:
74cf82fc2bc0a400ca64c66d45064847
Power PC Platform:
SUSE LINUX 10.1:
1c832fcde7f65332e9d0b47274229f69
7f303f1eeccd68a1eee8057f56807a3f
SUSE LINUX 10.0:
542ae786e2cb511767c7a4e6449b80cf
178014fc85ec3a0ca43ed9b8ed1cdd26
x86-64 Platform:
SUSE LINUX 10.1:
30ca5d51e0f3e889b31a59bad4611dfc
2990cb62f731d700675a75203bbd5aa7
SUSE LINUX 10.0:
542b66bcc88e07faec6c33abda8f5d7c
7a936eff6d66a5574e564c4255e3fa46
SUSE LINUX 9.3:
bd6cc27b6b9e05441bacdba249357f5d
Sources:
SUSE LINUX 10.1:
b04b4bb194dfbf4ea92b822149bd3664
SUSE LINUX 10.0:
ff3b7fd57d84597700a75f95fbfcc3e7
SUSE LINUX 9.3:
b53b87038538e026052356b8a89a0f82
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/c4745f0c0b9184f32b2201f189dc66f6.html
SuSE Linux Openexchange Server 4
http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html
Open Enterprise Server
http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html
Novell Linux POS 9
http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html
SuSE Linux Enterprise Server 8
http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html
SuSE Linux Standard Server 8
http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html
SuSE Linux School Server
http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html
SUSE LINUX Retail Solution 8
http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html
SUSE SLES 10
http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html
SUSE SLED 10
http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html
SUSE SLES 9
http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.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:
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.
====================================================================