Get the LinuxSecurity news you want faster with RSS
Powered By
SuSE: MozillaThunderbird various problems
Posted by Benjamin D. Thomas
Multiple vulnerabilities fixed.
______________________________________________________________________________
SUSE Security Announcement
Package: MozillaThunderbird
Announcement ID: SUSE-SA:2006:022
Date: Tue, 25 Apr 2006 15:00:00 +0000
Affected Products: SUSE LINUX 10.0
SUSE LINUX 9.3
SUSE LINUX 9.2
SUSE LINUX 9.1
Vulnerability Type: remote code execution
Severity (1-10): 8
SUSE Default Package: no
Cross-References: CVE-2004-1316, CVE-2005-0142, CVE-2005-0149
CVE-2005-0230, CVE-2005-0255, CVE-2005-0399
CVE-2005-0587, CVE-2005-0590, CVE-2005-0592
CVE-2005-0989, CVE-2005-1159, CVE-2005-1160
CVE-2005-1532, CVE-2005-2261, CVE-2005-2265
CVE-2005-2266, CVE-2005-2269, CVE-2005-2270
CVE-2005-2706, CVE-2005-2707, CVE-2006-0292
CVE-2006-0296, CVE-2006-0748, CVE-2006-0749
CVE-2006-0884, CVE-2006-1045, CVE-2006-1727
CVE-2006-1728, CVE-2006-1730, CVE-2006-1731
CVE-2006-1732, CVE-2006-1733, CVE-2006-1734
CVE-2006-1735, CVE-2006-1737, CVE-2006-1739
CVE-2006-1741, CVE-2006-1742, MFSA 2005-02
MFSA 2005-06, MFSA 2005-11, MFSA 2005-15
MFSA 2005-17, MFSA 2005-18, MFSA 2005-21
MFSA 2005-25, MFSA 2005-30, MFSA 2005-33
MFSA 2005-40, MFSA 2005-41, MFSA 2005-44
MFSA 2005-46, MFSA 2005-50, MFSA 2005-52
MFSA 2005-55, MFSA 2005-56, MFSA 2005-58
MFSA 2005-59, MFSA 2006-01, MFSA 2006-05
MFSA 2006-09, MFSA 2006-10, MFSA 2006-11
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-24
MFSA 2006-25, MFSA 2006-26, MFSA 2006-27
Content of This Advisory:
1) Security Vulnerability Resolved:
various Mozilla Thunderbird 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
Various security bugs have been fixed in Mozilla Thunderbird, bringing
it up to bugfix level of version 1.0.8.
This also catches up on earlier Thunderbird security releases.
Detailed list of issues and affected SUSE Linux versions:
Fixed in Thunderbird 1.0.8 (SUSE Linux 9.1, 9.2, 9.3 and 10.0)
MFSA 2006-27/CVE-2006-0748 - Table Rebuilding Code Execution Vulnerability
MFSA 2006-26/CVE-2006-1045 - Mail Multiple Information Disclosure
MFSA 2006-25/CVE-2006-1727 - Privilege escalation through Print Preview
MFSA 2006-24/CVE-2006-1728 - Privilege escalation using crypto.generateCRMFRequest
MFSA 2006-22/CVE-2006-1730 - CSS Letter-Spacing Heap Overflow Vulnerability
MFSA 2006-21/CVE-2006-0884 - JavaScript execution in mail when forwarding in-line
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 function's cloned parent
MFSA 2006-14/CVE-2006-1735 - Privilege escalation via XBL.method.eval
MFSA 2006-11/CVE-2006-1737/CVE-2006-1739 - 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
MFSA 2006-05/CVE-2006-0296 - Localstore.rdf XML injection through XULDocument.persist()
MFSA 2006-01/CVE-2006-0292 - JavaScript garbage-collection hazards
Fixed in Thunderbird 1.0.7 (SUSE Linux 9.1, 9.2, 9.3 and 10.0)
MFSA 2005-59/CVE-2005-2707 - Command-line handling on Linux allows shell execution
MFSA 2005-58/CVE-2005-2706 - Firefox 1.0.7 / Mozilla Suite 1.7.12 Vulnerability Fixes
Fixed in Thunderbird 1.0.5/1.0.6 (SUSE Linux 9.1, 9.2 and 9.3)
MFSA 2005-56/CVE-2005-2270 - Code execution through shared function objects
MFSA 2005-55/CVE-2005-2269 - XHTML node spoofing
MFSA 2005-52/CVE-2005-2266 - Same origin violation: frame calling top.focus()
MFSA 2005-50/CVE-2005-2265 - Exploitable crash in InstallVersion.compareTo()
MFSA 2005-46/CVE-2005-2261 - XBL scripts ran even when Javascript disabled
MFSA 2005-44/CVE-2005-1532 - Privilege escalation via non-DOM property overrides
MFSA 2005-41/CVE-2005-1160 - Privilege escalation via DOM property overrides
MFSA 2005-40/CVE-2005-1159 - Missing Install object instance checks
MFSA 2005-33/CVE-2005-0989 - Javascript "lambda" replace exposes memory contents
Fixed in Thunderbird 1.0.2 (SUSE Linux 9.1, 9.2 and 9.3)
MFSA 2005-30/CVE-2005-0399 - GIF heap overflow parsing Netscape extension 2
MFSA 2005-25/CVE-2005-0230 - Image drag and drop executable spoofing
MFSA 2005-21/CVE-2005-0587 - Overwrite arbitrary files downloading .lnk twice
MFSA 2005-18/CVE-2005-0255 - Memory overwrite in string library
MFSA 2005-17/CVE-2005-0590 - Install source spoofing with user:pass@host
MFSA 2005-15/CVE-2005-0592 - Heap overflow possible in UTF8 to Unicode conversion
Fixed in Thunderbird 1.0 (SUSE Linux 9.1 and 9.2)
MFSA 2005-11/CVE-2005-0149 - Mail client responds to cookie requests
Fixed in Thunderbird 0.9 (SUSE Linux 9.1 and 9.2)
MFSA 2005-06/CVE-2004-1316 - Heap overrun handling malicious news: URL
MFSA 2005-02/CVE-2005-0142 - Opened attachments are temporarily saved world-readable
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
See SUSE Security Summary Report.
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:
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/MozillaThunderbird-1.0.8-0.2.i586.rpm
26cf86fce7501020613b5e7aa9d817c0
SUSE LINUX 9.3:
ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/MozillaThunderbird-1.0.8-0.2.i586.rpm
cc56fcd7d79bdea6fe3f88fae36013e2
SUSE LINUX 9.2:
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/MozillaThunderbird-1.0.8-0.2.i586.rpm
1808acacd53e3248ac1b73c3b7d70557
SUSE LINUX 9.1:
ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/MozillaThunderbird-1.0.8-0.1.i586.rpm
c9ba754c65a76f7a7aae082b217b1add
Power PC Platform:
SUSE LINUX 10.0:
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/MozillaThunderbird-1.0.8-0.2.ppc.rpm
5ae486f9a4b72a632f1cd9bb6f5ae659
x86-64 Platform:
SUSE LINUX 10.0:
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/MozillaThunderbird-1.0.8-0.2.x86_64.rpm
d798bd7e1b8c964ac6be1e46be870a34
SUSE LINUX 9.3:
ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/MozillaThunderbird-1.0.8-0.2.x86_64.rpm
ddf99f2f040e5d559749b789bf2316d2
SUSE LINUX 9.2:
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/MozillaThunderbird-1.0.8-0.2.x86_64.rpm
67e96c7a21aa0bcfdea9ce1e003b02f2
SUSE LINUX 9.1:
ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/MozillaThunderbird-1.0.8-0.1.x86_64.rpm
6705eb87ba914bfdc40b2af96b89e771
Sources:
SUSE LINUX 10.0:
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/src/MozillaThunderbird-1.0.8-0.2.src.rpm
a1d223c8c5baca6a3e156a7f574033f0
SUSE LINUX 9.3:
ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/src/MozillaThunderbird-1.0.8-0.2.src.rpm
69aa14a7c43b0bdae68a7777c8e70a94
SUSE LINUX 9.2:
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/MozillaThunderbird-1.0.8-0.2.src.rpm
d7101dcb24d6686eaaa9d448a61ff49c
SUSE LINUX 9.1:
ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/MozillaThunderbird-1.0.8-0.1.src.rpm
2ddffcab2830abaac80470d1da121e1c
ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/MozillaThunderbird-1.0.8-0.1.src.rpm
c26b9d2f04a22a09da5393baa4a8e5e7
______________________________________________________________________________
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
none
______________________________________________________________________________
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.
=====================================================================
______________________________________________________________________________
The information in this advisory may be distributed or reproduced,
provided that the advisory is not modified in any way. In particular, the
clear text signature should show proof of the authenticity of the text.
SUSE Linux Products GmbH provides no warranties of any kind whatsoever
with respect to the information contained in this security advisory.