|
| Wed, Jan 07th | home | browse | articles | contact | chat | submit | faq | newsletter | about | stats | scoop | 17:31 UTC |
|
login « register « recover password « |
| [Article] | add comment | [Article] |
Mozilla Firefox was updated to version 2.0.0.15, fixing various bugs including a number of security bugs. Mozilla developers 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. Mozilla contributor moz_bug_r_a4 submitted a set of vulnerabilities which allow scripts from one document to be executed in the context of a different document. These vulnerabilities could be used by an attacker to violate the same-origin policy and perform an XSS attack. Security researcher Collin Jackson reported a series of vulnerabilities which allow JavaScript to be injected into signed JARs and executed under the context of the JAR's signer. This could allow an attacker to run JavaScript in a victim's browser with the privileges of a different website, provided the attacker possesses a JAR signed by the other website. Mozilla contributor moz_bug_r_a4 reported a vulnerability that allowed non-privileged XUL documents to load chrome scripts from the fastload file. This could allow an attacker to run arbitrary JavaScript code with chrome privileges. Mozilla contributor moz_bug_r_a4 reported a vulnerability which allows arbitrary JavaScript to be executed with chrome privileges. The privilege escalation was possible because JavaScript loaded via mozIJSSubScriptLoader.loadSubScript() was not using XPCNativeWrappers when accessing content. This could allow an attacker to overwrite trusted objects with arbitrary code which would be executed with chrome privileges when the trusted objects were called by the browser. Opera developer Claudio Santambrogio reported a vulnerability which allows malicious content to force the browser into uploading local files to the remote server. This could be used by an attacker to steal arbitrary files from a victim's computer. Security researcher Gregory Fleischer reported a vulnerability in the way Mozilla indicates the origin of a document to the Java plugin. This vulnerability could allow a malicious Java applet to bypass the same-origin policy and create arbitrary socket connections to other domains. Mozilla developer Daniel Glazman demonstrated that an improperly encoded .properties file in an add-on can result in uninitialized memory being used. This could potentially result in small chunks of data from other programs being exposed in the browser. Mozilla contributor Masahiro Yamada reported that file URLs in directory listings were not being HTML escaped properly when the filenames contained particular characters. This resulted in files from directory listings being opened in unintended ways or files not being able to be opened by the browser altogether. Mozilla developer John G. Myers reported a weakness in the trust model used by Mozilla regarding alternate names on self-signed certificates. A user could be prompted to accept a self-signed certificate from a website which includes alt-name entries. If the user accepted the certificate, they would also extend trust to any alternate domains listed in the certificate, despite not being prompted about the additional domains. This technique could be used by an attacker to impersonate another server. Mozilla community member Geoff reported a vulnerability in the way Mozilla opens URL files sent directly to the browser. He demonstrated that such files were opened with local file privileges, giving the remote content access to read from the local filesystem. If a user opened a bookmark to a malicious page in this manner, the page could potentially read from other local files on the user's computer. Security research firm Astabis, via the iSIGHT Partners GVP Program, reported a vulnerability in Mozilla's block reflow code. This vulnerability could be used by an attacker to crash the browser and run arbitrary code on the victim's computer. Fixed packages are available from ftp.suse.com. Links: ftp.suse.com -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: MozillaFirefox
Announcement ID: SUSE-SA:2008:034
Date: Fri, 11 Jul 2008 10:00:00 +0000
Affected Products: openSUSE 10.2
openSUSE 10.3
SUSE Linux Enterprise Desktop 10 SP1
SUSE Linux Enterprise Server 10 SP1
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-2008-2798, CVE-2008-2799, CVE-2008-2800
CVE-2008-2801, CVE-2008-2802, CVE-2008-2803
CVE-2008-2805, CVE-2008-2806, CVE-2008-2807
CVE-2008-2808, CVE-2008-2809, CVE-2008-2810
CVE-2008-2811, MFSA 2008-21, MFSA 2008-22
MFSA 2008-23, MFSA 2008-24, MFSA 2008-25
MFSA 2008-27, MFSA 2008-28, MFSA 2008-29
MFSA 2008-30, MFSA 2008-31, MFSA 2008-32
MFSA 2008-33
Content of This Advisory:
1) Security Vulnerability Resolved:
Mozilla Firefox 2.0.0.15 security update
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
Mozilla Firefox was updated to version 2.0.0.15, fixing various bugs
including following security bugs.
CVE-2008-2798 CVE-2008-2799 MFSA 2008-21:
Mozilla developers 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.
CVE-2008-2800 MFSA 2008-22:
Mozilla contributor moz_bug_r_a4 submitted a set of vulnerabilities
which allow scripts from one document to be executed in the context
of a different document. These vulnerabilities could be used by an
attacker to violate the same-origin policy and perform an XSS attack.
CVE-2008-2801 MFSA 2008-23:
Security researcher Collin Jackson reported a series of vulnerabilities
which allow JavaScript to be injected into signed JARs and executed
under the context of the JAR's signer. This could allow an attacker
to run JavaScript in a victim's browser with the privileges of a
different website, provided the attacker possesses a JAR signed by
the other website.
CVE-2008-2802 MFSA 2008-24:
Mozilla contributor moz_bug_r_a4 reported a vulnerability that
allowed non-privileged XUL documents to load chrome scripts from
the fastload file. This could allow an attacker to run arbitrary
JavaScript code with chrome privileges.
CVE-2008-2803 MFSA 2008-25:
Mozilla contributor moz_bug_r_a4 reported a vulnerability which allows
arbitrary JavaScript to be executed with chrome privileges. The
privilege escalation was possible because JavaScript loaded via
mozIJSSubScriptLoader.loadSubScript() was not using XPCNativeWrappers
when accessing content. This could allow an attacker to overwrite
trusted objects with arbitrary code which would be executed with
chrome privileges when the trusted objects were called by the browser.
CVE-2008-2805 MFSA 2008-27:
Opera developer Claudio Santambrogio reported a vulnerability which
allows malicious content to force the browser into uploading local
files to the remote server. This could be used by an attacker to
steal arbitrary files from a victim's computer.
CVE-2008-2806 MFSA 2008-28:
Security researcher Gregory Fleischer reported a vulnerability
in the way Mozilla indicates the origin of a document to the Java
plugin. This vulnerability could allow a malicious Java applet to
bypass the same-origin policy and create arbitrary socket connections
to other domains.
CVE-2008-2807 MFSA 2008-29:
Mozilla developer Daniel Glazman demonstrated that an improperly
encoded .properties file in an add-on can result in uninitialized
memory being used. This could potentially result in small chunks of
data from other programs being exposed in the browser.
CVE-2008-2808 MFSA 2008-30:
Mozilla contributor Masahiro Yamada reported that file URLs in
directory listings were not being HTML escaped properly when the
filenames contained particular characters. This resulted in files
from directory listings being opened in unintended ways or files not
being able to be opened by the browser altogether.
CVE-2008-2809 MFSA 2008-31:
Mozilla developer John G. Myers reported a weakness in the trust
model used by Mozilla regarding alternate names on self-signed
certificates. A user could be prompted to accept a self-signed
certificate from a website which includes alt-name entries. If
the user accepted the certificate, they would also extend trust to
any alternate domains listed in the certificate, despite not being
prompted about the additional domains. This technique could be used
by an attacker to impersonate another server.
CVE-2008-2810 MFSA 2008-32:
Mozilla community member Geoff reported a vulnerability in the way
Mozilla opens URL files sent directly to the browser. He demonstrated
that such files were opened with local file privileges, giving the
remote content access to read from the local filesystem. If a user
opened a bookmark to a malicious page in this manner, the page could
potentially read from other local files on the user's computer.
CVE-2008-2811 MFSA 2008-33:
Security research firm Astabis, via the iSIGHT Partners GVP Program,
reported a vulnerability in Mozilla's block reflow code. This
vulnerability could be used by an attacker to crash the browser and
run arbitrary code on the victim's computer.
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 Firefox 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
|