-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: MozillaFirefox,MozillaThunderbird
Announcement ID: SUSE-SA:2006:080
Date: Fri, 29 Dec 2006 15:00:00 +0000
Affected Products: Novell Linux Desktop 9
openSUSE 10.2
SUSE LINUX 10.1
SUSE LINUX 10.0
SUSE LINUX 9.3
SUSE SLED 10
SUSE SLES 10
Vulnerability Type: remote code execution
Severity (1-10): 7
SUSE Default Package: yes
Cross-References: CVE-2006-6497, CVE-2006-6498, CVE-2006-6499
CVE-2006-6500, CVE-2006-6501, CVE-2006-6502
CVE-2006-6503, CVE-2006-6504, CVE-2006-6505
CVE-2006-6506, CVE-2006-6507
Content of This Advisory:
1) Security Vulnerability Resolved:
various security problem in Mozilla programs
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
This security update brings the current set of Mozilla security updates, with
following versions:
- Mozilla Firefox to version 1.5.0.9 for Novell Linux Desktop 9,
SUSE Linux Enterprise 10 and SUSE Linux 9.3 up to 10.1.
- Mozilla Firefox to version 2.0.0.1 for openSUSE 10.2.
- Mozilla Thunderbird to version 1.5.0.9 for SUSE Linux 9.3 up to
10.1 and openSUSE 10.2.
These updates were released on December 22nd but due to Christmas
holidays got announced today.
Updated Seamonkey packages will be released soon.
More Details regarding the problems can be found on this page:
https://www.mozilla.org/en-US/security/known-vulnerabilities/
The updated packages includes fixes to the following security problems:
CVE-2006-6497/MFSA-2006-68: Crashes with evidence of memory corruption were fixed in the layout engine.
CVE-2006-6498/MFSA-2006-68: Crashes with evidence of memory corruption were fixed in the javascript engine.
CVE-2006-6499/MFSA-2006-68: Crashes regarding floating point usage were fixed.
CVE-2006-6500/MFSA-2006-69: This issue only affects Windows systems, Linux is not affected.
CVE-2006-6501/MFSA-2006-70: A privilege escalation using a watch point was fixed.
CVE-2006-6502/MFSA-2006-71: A LiveConnect crash finalizing JS objects was fixed.
CVE-2006-6503/MFSA-2006-72: A XSS problem caused by setting img.src to javascript: URI was fixed.
CVE-2006-6504/MFSA-2006-73: A Mozilla SVG Processing Remote Code Execution was fixed.
CVE-2006-6505/MFSA-2006-74: Some Mail header processing heap overflows were fixed.
CVE-2006-6506/MFSA-2006-75: The RSS Feed-preview referrer leak was fixed.
CVE-2006-6507/MFSA-2006-76: A XSS problem using outer window's Function object was fixed.
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 Mozilla Firefox and Thunderbird 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:
eea9f40b409823d691ad0e1b3daf5a82
dc5e760f067b2d1ea41be90c92517a5d
0b3638d9bfccfca0cf149df1200e6c47
d51cb9ff1cb3f5875cb4fa60b58f159b
SUSE LINUX 10.1:
fa3a6d10cb1a6dd801668e8881424036
a40dc8d7e29aa8bb21ecb3c348e0cc05
3bbfce9a8abf9394959348e449b35b95
869cac360c49cc15358b205923f2ee1d
SUSE LINUX 10.0:
f0b6bd1b56b874eb0003752cd112d6db
1722380cad796cc29d15374f7c471f09
82d7d8847f363a9e46fc9d22aa44f0c8
SUSE LINUX 9.3:
06b3af42ed8f528a306650691558301f
be42160ef33ead2625b20043267c2ce2
239aa22605bbd7c89a8489fb49c51f5d
Power PC Platform:
openSUSE 10.2:
c9611899a9bed84f006f8451dfcc44ae
e539db36e921505166e238a5aa853750
0d0b60cf410588c59003d04ab0ce0b33
0445e6652c8862691426ed623db2b362
SUSE LINUX 10.1:
3d399bf2bab2611809add386b63c085a
4a0223d379107cc45ef13d59369914dd
a795cd195043826ab0c9227251058905
a2c70ba35f54ff5cf7970d05940f00ee
SUSE LINUX 10.0:
72520bda4b0156991ce85e34eeef90a9
9d7f48fdce0092b7e00920ead4db56dc
aea7d9cfe7b9b95ddd0761bf4fce7fc1
x86-64 Platform:
openSUSE 10.2:
941d4d0e8a4332e3d585b67347d3bfaf
21cbeb89fcad730aecb715d92bdc9521
edc263e07b53d019e0d686c2134dddf5
f4f8dedac060cbd33f4b480aacb05bef
SUSE LINUX 10.1:
37f2af41fa077600d68df74547da4339
094c3157d83486a2fb10f0e3bb365a0a
SUSE LINUX 10.0:
f78215541f3b1f1af4aeba8b7414e907
SUSE LINUX 9.3:
dff09a04cd253fdcf830f93aa10edf49
Sources:
openSUSE 10.2:
8bdf86d5275d649f546a22c63a4b8cfb
223fff785e9e86fd5cbe0106ab1a5ddf
SUSE LINUX 10.1:
38373d35abf94ec8c0a2008dd1b6fc0d
184a16b5b80bd056a9526873756b75a5
SUSE LINUX 10.0:
62ade9bd59c8da0e9b739e59a8247708
2ec8f62cf812e2ea756e618c941fbdb5
SUSE LINUX 9.3:
c4444ff036405a4baa37c33b975941fa
14f7289ab7a5a2fcfd6cedf2acda628b
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
Novell Linux Desktop 9
SUSE SLES 10
SUSE SLED 10
http://support.novell.com/techcenter/psdb/5f62b1276a8877510b3124f13b3c3b27.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.
====================================================================
