The Mozilla Firefox browser is updated to version 3.0.6 fixing various security and stability issues.

MFSA 2009-01 / CVE-2009-0352 / CVE-2009-0353: 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.

MFSA 2009-02 / CVE-2009-0354: Mozilla security researcher moz_bug_r_a4 reported that a chrome XBL method can be used in conjuction with window.eval to execute arbitrary JavaScript within the context of another website, violating the same origin policy. Firefox 2 releases are not affected.

MFSA 2009-03 / CVE-2009-0355: Mozilla security researcher moz_bug_r_a4 reported that a form input control's type could be changed during the restoration of a closed tab. An attacker could set an input control's text value to the path of a local file whose location was known to the attacker. If the tab was then closed and the victim persuaded to re-open it, upon restoring the tab the attacker could use this vulnerability to change the input type to file. Scripts in the page could then automatically submit the form and steal the contents of the user's local file.

MFSA 2009-04 / CVE-2009-0356: Mozilla security researcher Georgi Guninski reported that the fix for an earlier vulnerability reported by Liu Die Yu using local internet shortcut files to access other sites (MFSA 2008-47) could be bypassed by redirecting to a privileged about: URI such as about:plugins. If an attacker could get a victim to download two files, a malicious HTML file and a .desktop shortcut file, they could have the HTML document load a privileged chrome document via the shortcut and both documents would be treated as same origin. This vulnerability could potentially be used by an attacker to inject arbitrary code into the chrome document and execute with chrome privileges. Because this attack has relatively high complexity, the severity of this issue was determined to be moderate.

MFSA 2009-05 / CVE-2009-0357: Developer and Mozilla community member Wladimir Palant reported that cookies marked HTTPOnly were readable by JavaScript via the XMLHttpRequest.getResponseHeader and XMLHttpRequest.getAllResponseHeaders APIs. This vulnerability bypasses the security mechanism provided by the HTTPOnly flag which intends to restrict JavaScript access to document.cookie. The fix prevents the XMLHttpRequest feature from accessing the Set-Cookie and Set-Cookie2 headers of any response whether or not the HTTPOnly flag was set for those cookies.

MFSA 2009-06 / CVE-2009-0358: Paul Nel reported that certain HTTP directives to not cache web pages, Cache-Control: no-store and Cache-Control: no-cache for HTTPS pages, were being ignored by Firefox 3. On a shared system, applications relying upon these HTTP directives could potentially expose private data. Another user on the system could use this vulnerability to view improperly cached pages containing private data by navigating the browser back.

Several flaws were found in the processing of malformed web content. A web page containing malicious content could cause Firefox to crash or, potentially, execute arbitrary code as the user running Firefox.
(CVE-2009-0352, CVE-2009-0353, CVE-2009-0356)

Several flaws were found in the way malformed content was processed. A website containing specially crafted content could, potentially, trick a Firefox user into surrendering sensitive information.
(CVE-2009-0354, CVE-2009-0355)

A flaw was found in the way Firefox treated HTTPOnly cookies. An attacker able to execute arbitrary JavaScript on a target site using HTTPOnly cookies may be able to use this flaw to steal the cookie.
(CVE-2009-0357)

A flaw was found in the way Firefox treated certain HTTP page caching directives. A local attacker could steal the contents of sensitive pages which the page author did not intend to be cached.
(CVE-2009-0358)

After installing the update, Firefox must be restarted for the changes to take effect.

The installed version of Firefox 3.0.x is earlier than 3.0.6.  Such versions are potentially affected by the following security issues :

  - There are several stability bugs in the browser engine     that could lead to crashes with evidence of memory     corruption. (MFSA 2009-01)

  - A chrome XBL method can be used in conjunction with     'window.eval' to execute arbitrary JavaScript within     the context of another website, violating the same     origin policy. (MFSA 2009-02)

  - A form input control's type could be changed during the     restoration of a closed tab to the path of a local file     whose location was known to the attacker. (MFSA 2009-03)

  - An attacker may be able to inject arbitrary code into a     chrome document and then execute it with chrome     privileges if he can trick a user into downloading a     malicious HTML file and a .desktop shortcut file.     (MFSA 2009-04)

  - Cookies marked HTTPOnly are readable by JavaScript via     the 'XMLHttpRequest.getResponseHeader' and     'XMLHttpRequest.getAllResponseHeaders' APIs.     (MFSA 2009-05)

  - The 'Cache-Control: no-store' and 'Cache-Control:     no-cache' HTTP directives for HTTPS pages are ignored     by Firefox 3, which could lead to exposure of     sensitive information. (MFSA 2009-06)

Several flaws were found in the processing of malformed web content. A web page containing malicious content could cause SeaMonkey to crash or, potentially, execute arbitrary code as the user running SeaMonkey.
(CVE-2009-0352, CVE-2009-0353)

A flaw was found in the way malformed content was processed. A website containing specially crafted content could, potentially, trick a SeaMonkey user into uploading a local file. (CVE-2009-0355)

A flaw was found in the way SeaMonkey treated HTTPOnly cookies. An attacker able to execute arbitrary JavaScript on a target site using HTTPOnly cookies may be able to use this flaw to steal the cookie.
(CVE-2009-0357)

After installing the update, SeaMonkey must be restarted for the changes to take effect.

From Red Hat Security Advisory 2009:0257 :

Updated SeaMonkey packages that fix security issues are now available for Red Hat Enterprise Linux 2.1, 3, and 4.

This update has been rated as having critical security impact by the Red Hat Security Response Team.

SeaMonkey is an open source Web browser, email and newsgroup client, IRC chat client, and HTML editor.

Several flaws were found in the processing of malformed web content. A web page containing malicious content could cause SeaMonkey to crash or, potentially, execute arbitrary code as the user running SeaMonkey.
(CVE-2009-0352, CVE-2009-0353)

A flaw was found in the way malformed content was processed. A website containing specially crafted content could, potentially, trick a SeaMonkey user into uploading a local file. (CVE-2009-0355)

A flaw was found in the way SeaMonkey treated HTTPOnly cookies. An attacker able to execute arbitrary JavaScript on a target site using HTTPOnly cookies may be able to use this flaw to steal the cookie.
(CVE-2009-0357)

All SeaMonkey users should upgrade to these updated packages, which contain backported patches that correct these issues. After installing the update, SeaMonkey must be restarted for the changes to take effect.

Versions of Firefox 3.x prior to 3.0.6 are affected by the following security issues : 

 - There are several stability bugs in the browser engine that may lead to crashes with evidence of memory corruption. (MFSA 2009-01)
 - A chrome XBL method can be used in conjunction with 'window.eval' to execute arbitrary JavaScript within the context of another website, violating the same origin policy. (MFSA 2009-02)
 - A form input control's type could be changed during the restoration of a closed tab to the path of a local file whose location was known to the attacker. (MFSA 2009-03)
 - An attacker may be able to inject arbitrary code into a chrome document and then execute it with chrome privileges if he can trick a user into downloading a malicious HTML file and a .desktop shortcut file. (MFSA 2009-04)
 - Cookies marked HTTPOnly are readable by JavaScript via the 'XMLHttpRequest.getResponseHeader' and 'XMLHttpRequest.getAllResponseHeaders' APIs.  (MFSA 2009-05)
 - The 'Cache-Control:  no-store' and 'Cache-Control:  no-cache' HTTP directives for HTTPS pages are ignored by Firefox 3, which could lead to exposure of sensitive information. (MFSA 2009-06).

The installed version of SeaMonkey is earlier than 1.1.15.  Such versions are potentially affected by the following security issues : 

  - There are several stability bugs in the browser engine that may lead to crashes with evidence of memory corruption. (MFSA 2009-01)

  - Cookies marked HTTPOnly are readable by JavaScript via the 'XMLHttpRequest.getResponseHeader' and 'XMLHttpRequest.getAllResponseHeaders' APIs. (MFSA 2009-05)

  - By exploiting stability bugs in the browser engine, it might be possible for an attacker to execute arbitrary code on the remote system under certain conditions. (MFSA 2009-07)

  - It may be possible for a website to read arbitrary XML data from another domain by using nsIRDFService and a cross-domain redirect. (MFSA 2009-09)

  - Vulnerabilities in the PNG libraries used by Mozilla could be exploited to execute arbitrary code on the remote system. (MFSA 2009-10)

Versions of Mozilla Thunderbird prior to 2.0.0.21 are affected by the following vulnerabilities :

 - There are several stability bugs in the browser engine that may lead to crashes with evidence of memory corruption. (MFSA 2009-01)
 - By exploiting stability bugs in the browser engine, it might be possible for an attacker to execute arbitrary code on the remote system under certain conditions. (MFSA 2009-07)
 - It may be possible for a website to read arbitrary XML data from another domain by using nsIRDFService and a cross-domain redirect. (MFSA 2009-09)
 - Vulnerabilities in the PNG libraries used by Mozilla could be exploited to execute arbitrary code on the remote system. (MFSA 2009-10)

The installed version of Firefox is earlier than 3.0.6.  Such versions are potentially affected by the following security issues : 

  - There are several stability bugs in the browser engine that may lead to crashes with evidence of memory corruption. (MFSA 2009-01)

  - A chrome XBL method can be used in conjunction with 'window.eval' to execute arbitrary JavaScript within the context of another website, violating the same origin policy. (MFSA 2009-02)

  - A form input control's type could be changed during the restoration of a closed tab to the path of a local file whose location was known to the attacker. (MFSA 2009-03)

  - An attacker may be able to inject arbitrary code into a chrome document and then execute it with chrome privileges if he can trick a user into downloading a malicious HTML file and a .desktop shortcut file. (MFSA 2009-04)

  - Cookies marked HTTPOnly are readable by JavaScript via the 'XMLHttpRequest.getResponseHeader' and 'XMLHttpRequest.getAllResponseHeaders' APIs.  (MFSA 2009-05)

  - The 'Cache-Control:  no-store' and 'Cache-Control:  no-cache' HTTP directives for HTTPS pages are ignored by Firefox 3, which could lead to exposure of sensitive information. (MFSA 2009-06).

The installed version of Thunderbird is earlier than 2.0.0.21.  Such versions are potentially affected by the following security issues : 

  - There are several stability bugs in the browser engine that may lead to crashes with evidence of memory corruption. (MFSA 2009-01)

  - By exploiting stability bugs in the browser engine, it might be possible for an attacker to execute arbitrary code on the remote system under certain conditions.  (MFSA 2009-07)

  - It may be possible for a website to read arbitrary XML data from another domain by using nsIRDFService and a cross-domain redirect. (MFSA 2009-09)

  - Vulnerabilities in the PNG libraries used by Mozilla could be exploited to execute arbitrary code on the remote system. (MFSA 2009-10)

ID	名前	製品	ファミリー	公開日	更新日	深刻度
39886	openSUSE Security Update : MozillaFirefox (MozillaFirefox-509)	Nessus	SuSE Local Security Checks	2009/7/21	2021/1/14	critical
60527	Scientific Linux Security Update : firefox on SL4.x, SL5.x i386/x86_64	Nessus	Scientific Linux Local Security Checks	2012/8/1	2021/1/14	critical
35581	Firefox 3.0.x < 3.0.6 Multiple Vulnerabilities	Nessus	Windows	2009/2/4	2018/7/16	high
60528	Scientific Linux Security Update : seamonkey on SL3.x, SL4.x i386/x86_64	Nessus	Scientific Linux Local Security Checks	2012/8/1	2021/1/14	critical
67796	Oracle Linux 3 / 4 : seamonkey (ELSA-2009-0257)	Nessus	Oracle Linux Local Security Checks	2013/7/12	2021/1/14	critical
4922	Mozilla Firefox 3.x < 3.0.6 Multiple Vulnerabilities	Nessus Network Monitor	Web Clients	2009/2/4	2019/3/6	medium
4965	SeaMonkey < 1.1.15 Multiple Vulnerabilities	Nessus Network Monitor	Web Clients	2009/3/23	2019/3/6	medium
4964	Mozilla Thunderbird < 2.0.0.21 Multiple Vulnerabilities	Nessus Network Monitor	SMTP Clients	2009/3/23	2019/3/6	medium
800752	Firefox < 3.0.6 Multiple Vulnerabilities	Log Correlation Engine	Web Clients			high
801212	Mozilla Thunderbird < 2.0.0.21 Multiple Vulnerabilities	Log Correlation Engine	SMTP Clients			high
800869	SeaMonkey < 1.1.15 Multiple Vulnerabilities	Log Correlation Engine	Web Clients			high

検出

プラグインの検索

critical

critical

high

critical

critical

medium

medium

medium

high

high

high