Package: MozillaFirefox
Announcement ID: SUSE-SA:2009:042
Date: Thu, 06 Aug 2009 10:00:00 +0000
Affected Products: SLE SDK 10 SP2
SUSE Linux Enterprise Desktop 10 SP2
SUSE Linux Enterprise 10 SP2 DEBUGINFO
SUSE Linux Enterprise Server 10 SP2
Vulnerability Type: remote code execution
Severity (1-10): 8
SUSE Default Package: yes
Cross-References: CVE-2009-1194, CVE-2009-2462, CVE-2009-2463
CVE-2009-2464, CVE-2009-2465, CVE-2009-2466
CVE-2009-2467, CVE-2009-2469, CVE-2009-2471
CVE-2009-2472, MFSA 2009-34, MFSA 2009-35
MFSA 2009-36, MFSA 2009-37, MFSA 2009-39
MFSA 2009-40
Content of This Advisory:
1) Security Vulnerability Resolved:
Mozilla Firefox 3.0 security version upgrade
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
The Mozilla Firefox Browser in SUSE Linux Enterprise 10 Service Pack 2
was brought from the old 2.0.0.x release branch to the current 3.0.12
release of the Firefox 3.0 release branch.
It contains the following new security fixes:
MFSA 2009-34 / CVE-2009-2462 / CVE-2009-2463 / CVE-2009-2464 /
CVE-2009-2465 / CVE-2009-2466:
Mozilla developers and community members identified and fixed
several stability bugs in the browser engine used in Firefox and
other Mozilla-based products. Some of these crashes showed evidence
of memory corruption under certain circumstances and we presume that
with enough effort at least some of these could be exploited to run
arbitrary code.
MFSA 2009-35 / CVE-2009-2467:
Security researcher Attila Suszter reported that when a page contains
a Flash object which presents a slow script dialog, and the page is
navigated while the dialog is still visible to the user, the Flash
plugin is unloaded resulting in a crash due to a call to the deleted
object. This crash could potentially be used by an attacker to run
arbitrary code on a victim's computer.
MFSA 2009-36 / CVE-2009-1194:
oCERT security researcher Will Drewry reported a series of heap
and integer overflow vulnerabilities which independently affected
multiple font glyph rendering libraries. On Linux platforms libpango
was susceptible to the vulnerabilities while on OS X CoreGraphics was
similarly vulnerable. An attacker could trigger these overflows by
constructing a very large text run for the browser to display. Such an
overflow can result in a crash which the attacker could potentially
use to run arbitrary code on a victim's computer. The open-source
nature of Linux meant that Mozilla was able to work with the libpango
maintainers to implement the correct fix in version 1.24 of that
system library which was distributed with OS security updates. On
Mac OS X Firefox works around the CoreGraphics flaw by limiting the
length of text runs passed to the system.
MFSA 2009-37 / CVE-2009-2469:
Security researcher PenPal reported a crash involving a SVG element on
which a watch function and __defineSetter__ function have been set for
a particular property. The crash showed evidence of memory corruption
and could potentially be used by an attacker to run arbitrary code
MFSA 2009-39 / CVE-2009-2471:
Mozilla developer Blake Kaplan reported that setTimeout, when called
with certain object parameters which should be protected with a
XPCNativeWrapper, will fail to keep the object wrapped when compiling
the new function to be executed. If chrome privileged code were
to call setTimeout using this as an argument, the this object will
lose its wrapper and could be unsafely accessed by chrome code. An
attacker could use such vulnerable code to run arbitrary JavaScript
with chrome privileges.
MFSA 2009-40 / CVE-2009-2472:
Mozilla security researcher moz_bug_r_a4 reported a series
of vulnerabilities in which objects that normally receive a
XPCCrossOriginWrapper are constructed without the wrapper. This
can lead to cases where JavaScript from one website may unsafely
access properties of such an object which had been set by a different
website. A malicious website could use this vulnerability to launch
a XSS attack and run arbitrary JavaScript within the context of
another site.
The update also contains a set of GTK2+ and dependend libraries
necessary for this version upgrade.
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
Please restart all running Firefox instances after the update.
This update is not yet available on S/390 64bit, this will be delivered
with the upcoming 3.0.13 update.
Due to a unclear SUN Java bug Firefox will not start on the first try,
but only on the second.
This update also requires a fixed yast2-registration, otherwise further
registration tasks will not open a webbrowser. It is available with
this 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
downloaded RPM package.
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
SUSE Linux Enterprise Server 10 SP2
http://download.novell.com/index.jsp?search=Search&set_restricted=true&keywords=3f7ea35ff3a66f8b5a66e5a57078af6e
http://download.novell.com/index.jsp?search=Search&set_restricted=true&keywords=61727c390a4b8913f47dbf3a493650a8
SLE SDK 10 SP2
http://download.novell.com/index.jsp?search=Search&set_restricted=true&keywords=61727c390a4b8913f47dbf3a493650a8
SUSE Linux Enterprise 10 SP2 DEBUGINFO
http://download.novell.com/index.jsp?search=Search&set_restricted=true&keywords=61727c390a4b8913f47dbf3a493650a8
SUSE Linux Enterprise Desktop 10 SP2
http://download.novell.com/index.jsp?search=Search&set_restricted=true&keywords=3f7ea35ff3a66f8b5a66e5a57078af6e
http://download.novell.com/index.jsp?search=Search&set_restricted=true&keywords=61727c390a4b8913f47dbf3a493650a8
______________________________________________________________________________
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
announcement. The output for a valid signature looks like:
gpg: Signature made
gpg: Good signature from "SuSE Security Team
where
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.
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
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.
- 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
opensuse-security-announce@opensuse.org
- 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
The
=====================================================================
______________________________________________________________________________
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.
Type Bits/KeyID Date User ID
pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key
