-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: w3m
Announcement ID: SUSE-SA:2007:005
Date: Wed, 10 Jan 2007 13:00:00 +0000
Affected Products: Novell Linux Desktop 9
Novell Linux POS 9
Open Enterprise Server
openSUSE 10.2
SUSE LINUX 10.1
SUSE LINUX 10.0
SUSE LINUX 9.3
SuSE Linux Desktop 1.0
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, remote code execution
Severity (1-10): 5
SUSE Default Package: yes
Cross-References: CVE-2006-6772
Content of This Advisory:
1) Security Vulnerability Resolved:
format string problem in w3m
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 format string problem in w3m -dump / -backend mode could be used
by a malicious server to crash w3m or execute code.
In SUSE Linux 10.1, openSUSE 10.2 and SUSE Linux Enterprise Server
and Desktop 10 this problem was not exploitable to execute code due
to use of the FORTIFY SOURCE extensions.
This problem is tracked by the Mitre CVE ID CVE-2006-6772.
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:
3525018108eef9575b49f83fff5d2ccc
SUSE LINUX 10.1:
30b208f9f0b2bab7f307992f5b9ba37a
SUSE LINUX 10.0:
2fe8c1e60e42d455f3a7893d746fed5b
SUSE LINUX 9.3:
e4d9b3249af7c1e30e952fed5f0ca715
Power PC Platform:
openSUSE 10.2:
0af57d2db4baee945906778928ba224c
SUSE LINUX 10.1:
8b82c09173486db5bd3e86e608eb8f03
SUSE LINUX 10.0:
cdacb01e8ff67ae2b6a9e8b50aca2ded
x86-64 Platform:
openSUSE 10.2:
e15ebe53773a96389d9c6f881c0b78fe
SUSE LINUX 10.1:
58f2eef278dd4d44353b7667cee9052e
SUSE LINUX 10.0:
7a55737fd8c21182155fc072a94effe6
SUSE LINUX 9.3:
e58ec0574d37df6c380ddfefc6ca8f2e
Sources:
openSUSE 10.2:
0586de642d025ad7cb90b322d13b6070
SUSE LINUX 10.1:
2b58129ee87210b76a4ed07fe98e9f4e
SUSE LINUX 10.0:
120ba25b2123467e4c7df451452c36a8
SUSE LINUX 9.3:
e6fccb4480b5d8e7445ad83fb1e6b43b
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/68d7a138079c9fa4fa2b1defabd0c5ab.html
SuSE Linux Openexchange Server 4
http://support.novell.com/techcenter/psdb/68d7a138079c9fa4fa2b1defabd0c5ab.html
Open Enterprise Server
http://support.novell.com/techcenter/psdb/68d7a138079c9fa4fa2b1defabd0c5ab.html
Novell Linux POS 9
http://support.novell.com/techcenter/psdb/68d7a138079c9fa4fa2b1defabd0c5ab.html
Novell Linux Desktop 9
http://support.novell.com/techcenter/psdb/68d7a138079c9fa4fa2b1defabd0c5ab.html
SuSE Linux Enterprise Server 8
http://support.novell.com/techcenter/psdb/68d7a138079c9fa4fa2b1defabd0c5ab.html
SuSE Linux Standard Server 8
http://support.novell.com/techcenter/psdb/68d7a138079c9fa4fa2b1defabd0c5ab.html
SuSE Linux School Server
http://support.novell.com/techcenter/psdb/68d7a138079c9fa4fa2b1defabd0c5ab.html
SUSE LINUX Retail Solution 8
http://support.novell.com/techcenter/psdb/68d7a138079c9fa4fa2b1defabd0c5ab.html
SuSE Linux Desktop 1.0
http://support.novell.com/techcenter/psdb/68d7a138079c9fa4fa2b1defabd0c5ab.html
SUSE SLES 10
http://support.novell.com/techcenter/psdb/68d7a138079c9fa4fa2b1defabd0c5ab.html
SUSE SLED 10
http://support.novell.com/techcenter/psdb/68d7a138079c9fa4fa2b1defabd0c5ab.html
SUSE SLES 9
http://support.novell.com/techcenter/psdb/68d7a138079c9fa4fa2b1defabd0c5ab.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.
====================================================================
