-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: MozillaFirefox,MozillaThunderbird,seamonkey
Announcement ID: SUSE-SA:2006:054
Date: Fri, 22 Sep 2006 15:00:00 +0000
Affected Products: Novell Linux Desktop 9
SUSE LINUX 10.1
SUSE LINUX 10.0
SUSE LINUX 9.3
SUSE LINUX 9.2
SUSE SLED 10
SUSE SLES 10
Vulnerability Type: remote code execution
Severity (1-10): 8
SUSE Default Package: yes
Cross-References: CVE-2006-4253, CVE-2006-4340, CVE-2006-4565
CVE-2006-4566, CVE-2006-4567, CVE-2006-4568
CVE-2006-4569, CVE-2006-4570, CVE-2006-4571
MFSA 2006-57, MFSA 2006-58, MFSA 2006-59
MFSA 2006-60, MFSA 2006-61, MFSA 2006-62
MFSA 2006-63, MFSA 2006-64
Content of This Advisory:
1) Security Vulnerability Resolved:
various Mozilla 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
Security updates have been released that bring Mozilla Firefox to
version 1.5.0.7, Mozilla Thunderbird to version 1.5.0.7 and Mozilla
Seamonkey to 1.0.5.
Seamonkey and Thunderbird were released early this week, Firefox was
released today.
Please also see
https://www.mozilla.org/en-US/security/known-vulnerabilities/
for more details.
The updates fix the following security problems:
MFSA 2006-64/CVE-2006-4571: Crashes with evidence of memory corruption
MFSA 2006-63/CVE-2006-4570: Executing JavaScript within E-Mail using XBL
MFSA 2006-62/CVE-2006-4569: Pop up-blocker cross-site scripting (XSS)
MFSA 2006-61/CVE-2006-4568: Frame spoofing using document.open()
MFSA 2006-60/CVE-2006-4340/CERT VU#845620: RSA Signature Forgery
MFSA 2006-59/CVE-2006-4253: Concurrency-related vulnerability
MFSA 2006-58/CVE-2006-4567: Auto-Update compromise through DNS and SSL spoofing
MFSA 2006-57/CVE-2006-4565/CVE-2006-4566: JavaScript Regular Expression Heap Corruption
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
or 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:
SUSE LINUX 10.1:
c2241c461583cb54da9444aa13513da8
cede57cc709d100a17747f87fbc8f02b
28bba6b62a42895ccd6df331a7926500
acee42b344e5e3a367d243aa417c12b3
75af4685ab07ddd80d95ff2b6f8fceef
5b25c1e00032672ec95245b9cb0dcf8a
430729d03b65c87f882d1e2997d316a8
d1f2779e225937c360cd9c68a583fc37
a471c1ded619519aa9ecbc9890a9382c
17dc992659486f8216549fc39cda55bd
88678b6dfda08966bb9994f081804b0c
SUSE LINUX 10.0:
e6d74190437f49b0fc5276f6b856b67e
225f846874b32245b23492d51bc077b3
39371eb2f03f8f90a4e8ffc4f29a182c
SUSE LINUX 9.3:
746a56a6aa9402287d7c0f054989689c
5ef6019c2a3b149e84073a699c178b27
05b9588e09dccfcc8e4b5320398ebd07
SUSE LINUX 9.2:
653f774d37b664ce97ecbb31bdca9041
dc8d989574b91fca7cc6d294469330e7
5e96afa8a01e9c487e46cfb144cea474
Power PC Platform:
SUSE LINUX 10.1:
c81caccf49c06e060b095c50c9241212
53e3e3acf042ccf76882d27bfd0b1bb8
3fb66e6bce779781cb25175f4ba029ed
d69cd7b2f1853b84a1f64f1187196f8e
5d81db21ab3ff65e2da8f7c7834c9dd7
195fe45f87de1625191df8fe9b56216a
d797584d1507df5cee459ae52025ae4f
ac452dc31a45124129faca0b7a289881
213ee0051aabeb1606128fdf031f87ec
7200d9d8f6de89125c12c18fb082ff92
0e51a3e3b0ea39f951bf146db8316995
SUSE LINUX 10.0:
c18441b3b260aeb26445bc6f514d76cf
22c3c4e9102e35bdcdccc9970bb8e86b
a27cfdf5824fe2155215806c3e48ef01
x86-64 Platform:
SUSE LINUX 10.1:
c8f0e029fd901c0ee4b792e657534094
6adbd489c023501639fd417844a4af6f
3134380adefa0d0eef28ceaea0feefa3
9264ba5a10f98dc9c4bc6b6bb3f948c9
2391b23a49e8044025feeba96f3c98aa
6e6de01bba861db89ae1cef20423f99b
d54a8f88541d6809b55510899ad60e9c
fd6847218166c1f3175fe5197d057340
36bff38cd92af4b4759805498c9f26fc
SUSE LINUX 10.0:
21dd3f6e951b6a26b423fef4446049a9
SUSE LINUX 9.3:
29a0d99e40b423720c412778f9c348c2
SUSE LINUX 9.2:
d9373f704a849e401296a6ce1029af8e
95e941405253b750c712008f8ede371e
db25bb261cefcc722e349450190ac0dc
Sources:
SUSE LINUX 10.1:
a84a3ced8c0f7c3222cc3ab76e51a2d9
63cb05e759521c36b28ca86b95e3008b
d5c0667bc7ac9899e5d083335259de32
SUSE LINUX 10.0:
9081b907a933f4112b1dea8501c5be8c
0af702b1eac30f7413b7959e08d92f4f
SUSE LINUX 9.3:
2cb13934696dc77c4a92cf6e51cb3947
70b0ce0a6abc740bb3b7564ee8d95de4
SUSE LINUX 9.2:
c56ba0432ded361fe09e7e12fec9ff48
56770bca1157d6e43e21ecd4fddcad51
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
Novell Linux Desktop 9
http://support.novell.com/techcenter/psdb/ef4a219c3a29a3b7d4c57c43cccd0acc.html
SUSE SLES 10
http://support.novell.com/techcenter/psdb/ef4a219c3a29a3b7d4c57c43cccd0acc.html
SUSE SLED 10
http://support.novell.com/techcenter/psdb/ef4a219c3a29a3b7d4c57c43cccd0acc.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.
====================================================================
