-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: MozillaFirefox,mozilla
Announcement ID: SUSE-SA:2006:021
Date: Thu, 20 Apr 2006 09:00:00 +0000
Affected Products: Novell Linux Desktop 9
SUSE LINUX 10.0
SUSE LINUX 9.3
SUSE LINUX 9.2
SUSE LINUX 9.1
SuSE Linux Desktop 1.0
SuSE Linux Enterprise Server 8
SUSE SLES 9
UnitedLinux 1.0
Vulnerability Type: remote code execution
Severity (1-10): 8
SUSE Default Package: yes
Cross-References: CVE-2006-0749, CVE-2006-0884, CVE-2006-1727
CVE-2006-1728, CVE-2006-1729, CVE-2006-1730
CVE-2006-1731, CVE-2006-1732, CVE-2006-1733
CVE-2006-1734, CVE-2006-1735, CVE-2006-1736
CVE-2006-1737, CVE-2006-1738, CVE-2006-1739
CVE-2006-1740, CVE-2006-1741, CVE-2006-1742
CVE-2006-1790
MFSA 2006-09, MFSA 2006-10, MFSA 2006-11
MFSA 2006-12, MFSA 2006-13, MFSA 2006-14
MFSA 2006-15, MFSA 2006-16, MFSA 2006-17
MFSA 2006-18, MFSA 2006-19, MFSA 2006-21
MFSA 2006-22, MFSA 2006-23, MFSA 2006-24
MFSA 2006-25
Content of This Advisory:
1) Security Vulnerability Resolved:
various security problems in Mozilla based browsers 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 number of security issues have been fixed in the Mozilla browser
suite and the Mozilla Firefox browser.
These problems could be used by remote attackers to gain privileges,
gain access to confidential information or to cause denial of service
attacks.
The updates of the Firefox packages bring it up to Firefox 1.0.8 fix level.
The updates of the Mozilla suite bring it up to Mozilla 1.7.13 fix level.
Mozilla Thunderbird is also affected by some of the listed issues, but
updates will be provided later due to unrelated problems. Most of them
can be worked around by turning Java Script in Mails off (which is the
default for Thunderbird).
Full details of all issues can be found on:
https://www.mozilla.org/en-US/security/advisories/
List of issues that were fixed:
MFSA 2006-25/CVE-2006-1727:
Privilege escalation through Print Preview
MFSA 2006-24/CVE-2006-1728:
Privilege escalation using crypto.generateCRMFRequest
MFSA 2006-23/CVE-2006-1729:
File stealing by changing input type
MFSA 2006-22/CVE-2006-1730:
CSS Letter-Spacing Heap Overflow Vulnerability
MFSA 2006-21/CVE-2006-0884:
Javascript execution when forwarding or replying
MFSA 2006-19/CVE-2006-1731
Cross-site scripting using .valueOf.call()
MFSA 2006-18/CVE-2006-0749
Mozilla Firefox Tag Order Vulnerability
MFSA 2006-17/CVE-2006-1732
Cross-site scripting through window.controllers MFSA 2006-16/CVE-2006-1733
Accessing XBL compilation scope via valueOf.call()
MFSA 2006-15/CVE-2006-1734
Privilege escalation using a JavaScript functions cloned parent
MFSA 2006-14/CVE-2006-1735
Privilege escalation via XBL.method.eval
MFSA 2006-13/CVE-2006-1736
Downloading executables with "Save Image As..."
MFSA 2006-12/CVE-2006-1740
Secure-site spoof (requires security warning dialog)
MFSA 2006-11/CVE-2006-1739,CVE-2006-1737,CVE-2006-1738,CVE-2006-1790
Crashes with evidence of memory corruption (rv:1.8)
MFSA 2006-10/CVE-2006-1742
JavaScript garbage-collection hazard audit
MFSA 2006-09/CVE-2006-1741
Cross-site JavaScript injection using event handlers
We wish to thank the Mozilla Developers and the various bug reporters for reporting and fixing those issues.
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.0:
fb4052fec7c505cf978cf93b743c47e7
03e0b30e4fd923cab1293709f151de01
3665a2a745b4900144a870b9bb31f874
2e652d6bdcf018d1aac6129048b6e1b0
d5609133dd3fd5d04fdf387b713359cf
084cae3650042f37cf431ff78c180cf5
410f4b58bb649ddc9a348b22bea45806
aded919e26dd202c071bde6db2c21348
ba9bfb8fcb10c815501dcf97f926d0d2
0390a6e264029285de559601d349b08e
SUSE LINUX 9.3:
f05d8e788e1260c1cd03db8bdd0c97a9
f56204a4ce738fcba25eab5f01fb0d1f
ca4ca4dbef3a034aec1c803d44afc59b
e2977217997dedb4355eed936c6ddf8e
e42f758657c7c463b8828824bc7b1c01
dea4ed050a93d4bd6e22cabda1ff3f07
d6fae5fa01350cac1c8f89461c0b4c3b
fe17c90d8d452597322c7a84152642fb
35bf127628cf57484199aa93da8af587
739736bdd0320bf63ac51816c300eed5
SUSE LINUX 9.2:
3bdb5eb69e19c6550d27e53e108163bd
533b00705c7c71cd9c0a7ef6e0111551
4166cec3090b0b9bb62872a4c32068e1
ac383edcd500e7ad90886d2d4fb88463
4da7e16ff221ed507c27eed2b4e860a0
b1febedbed9828e39e5fb5f7ac8866ad
d2afd4022d30c4cd285ab62cca32cefc
fe8903a19d08107d2ed1554aaea24443
4382ceace35e0ffd70f8422f09172b80
c9968cca9468bfed3122174372aa7abc
90d4a422d29f4a32f006184293987a87
4615c8bda70a37c3aebf9a8677fe2a55
032fe54bf4d0c318037cf3e021087a13
14c66250ea87a591cb5c7b6203a4f4db
46f294d0c19049c46d4f2624d7869d84
SUSE LINUX 9.1:
c2e2d1dfe3794e305d3360250e09b402
918d453f97b00a03a428e72245db345f
a6612bfcd38921697ca7ca51d7a76773
c22b7d0f8849dcc4035c8ea5bc7f87c4
aa9907a5db6b35b26fa33e64de996bdf
a8360af34d190e1fd56f086e11a5dfc4
a7105f26820e4dd8b79775b6de6e8311
037fc7410258acabde9d16bb780a38ff
e493b493eb10ec106a2aae5bfbcb7a59
9a5a53dca8fb9fc1fc47e7c20a038b6f
3f57af2b99449d03b2bf4bac79dde333
c70be9ea00333bc39692cf76b4fc9bd1
b52c57df906a390ad28761f52528871f
aecc152da7c5f08008162b29d3558708
f8a44e8c3819288f3bc93c6bbcfd1b7e
Power PC Platform:
SUSE LINUX 10.0:
99dc40383bf1a28b93bb2a09ad7f8dbf
f0b9c6d37821cada37954fd85dbdd792
75153437e729180992bf017efc61862f
8842635e83159b84c7cdbd1042a6ffd5
1bb665d46ca8b060905798276b3c9e70
3be663327e32b448098b61d2026424c9
c03d279acd8fb9adba94e26b9f270832
bd5a16852a6c848284905e9924899461
78c092fa49dfd5b7b7c838595e232512
ebdc386a57ed157e2bc913510b399bba
x86-64 Platform:
SUSE LINUX 10.0:
5193b67c01a9cf55343796affe383379
195d7c331ea931918a2a4cf5fc7f8d1b
e26b11522ef6d901d01d03ce45f1ef8d
fbf8e2451f3468141f79ad51da805867
b9c04f08c1729aa39ff27799736eecad
7fa9c180414bb49e9f85709ac79b89fe
3e5c312d230016ac4b3264bcf8132eea
4188c59f35557cb8218dca59eff65931
SUSE LINUX 9.3:
fc028b2876f496851cb9775f3b8dd28e
d0b235b85a84cee9510bf68ea26bb812
418758bc73b6b99d19f7cf08d132fed8
9ee68afcb6b027d7a390263b5159aedf
554400f6490c8907e775821354538e7f
5715c72f969bdfeeefe662a5b548857e
d0ec5930dfa372ff60b0f6c6d045ac98
7b20d985670575113d91d46052fbe8b1
f4abf5f846a77d9f74b9902283ffe816
SUSE LINUX 9.2:
a563f5e3b2d990d0569f254faaf4f988
c3fec28a26d6c994280ba6c79c18b8d6
1471b9687c9867d8552653dd57840cb4
df74eefcf9cc9e4f854261d27eefc44f
da5bc675b98d7e5241817dcd1f2928b0
a4be3a78469b1da4f9944a0d81060d29
14b773fb9edc662ebfde5b5e3f2cffd9
544bc0b32a53469297902f708a2bf8fa
7ba1e581b0b70f48b5a84504a2b3f71b
fb5186cf5baee601452407e059d1a098
d033108e17d91b8d200168265a799b62
b3989d03ac912f0a7cf6e87b76269ee6
3f347d5af79a8bd6678103b5c8502dbf
82f173f2ac63cba4c58ef166f965fa2d
60d581d068525e69144764aa1fc8eb46
SUSE LINUX 9.1:
f786317714fcdd3c5ccaf03ba1a6bb0c
6d69f456b637ab56476ceb824947554a
b97170e3a0265d2e0f07cb3100335d97
7328833bbe0de80023016192e5866986
5d2a8e865a8b28c6b7179423f1af8cec
29a0832fd67bef035d087920b69a14b4
0be3b29e2041dbe68d0c475ec736a493
699a4027e7cd328b2a1861c7bceec6b0
0f0dcbb0a0b89b72e5cd19775c461384
2f425551a415e8769fbf302a603423de
27bb7fe6ec834c2c5bfb0d04e12ad896
3759bf756b7acffcf10ba9a550561942
6c3eef33024331753e4f695b3a6e00b0
708a02c212ea10fc4f160aaa57cbe569
e50fb24ad56c317b1469d0921151a018
Sources:
SUSE LINUX 10.0:
1fa22913dce8f99ecb4acc82d2583e69
4322c44bb7dd884972fe55d7c8c2b9b0
SUSE LINUX 9.3:
2a86aa596f42a4b7305588033e006a71
aa3fab18bb80fafe4302c8337ed1a842
SUSE LINUX 9.2:
2bafd676fb4c5ce7635c0eaa3d871906
1a865de86712fc37bda0000f9cd7baeb
a4cb05881a7a5b3c5737a1fc594f6295
6bfc2a4a7e22d8f3ae7fa0a55a54fe65
a65f7696ea67ff048acbfbc0ebc26d77
SUSE LINUX 9.1:
94e98a241c0f61e78b612ba29889798a
114e587faaf22eda1fbcd61c7de3d3db
2904934349b71dd46b06ff21f9a951d7
f59abf296e089ae205c9928d6235a93f
728fd0459ee3eff4d7c158031f61d744
ec19f6afd795c481ac46e788ed7da58d
778baef80eae9f251588b97518a48680
09de83eaaa8e82e28c5b9f9babdaa2cb
166a523cf4ec0da51d67e41c4587b923
e2d2403ed6f9d9da2a4282ce29187ac9
ae665ce4b13e15f373c4f9c76d90d094
8469a85ef418bff47dae31510b556037
5a85134ab51d0566101c2abccf9dea45
d13efd21d0a25fc198c58db2850ce18c
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
______________________________________________________________________________
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.
====================================================================
