This update brings Mozilla SeaMonkey to the 2.0.6 security release.

It fixes following security bugs: MFSA 2010-34 / CVE-2010-1211:
Mozilla developers identified and fixed several memory safety bugs in the browser engine used in Firefox and other Mozilla-based products.
Some of these bugs 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. Jesse Ruderman, Ehsan Akhgari, Mats Palmgren, Igor Bukanov, Gary Kwong, Tobias Markus and Daniel Holbert reported memory safety problems that affected Firefox 3.6 and Firefox 3.5.

MFSA 2010-35 / CVE-2010-1208: Security researcher regenrecht reported via TippingPoint's Zero Day Initiative an error in the DOM attribute cloning routine where under certain circumstances an event attribute node can be deleted while another object still contains a reference to it. This reference could subsequently be accessed, potentially causing the execution of attacker controlled memory.

MFSA 2010-36 / CVE-2010-1209: Security researcher regenrecht reported via TippingPoint's Zero Day Initiative an error in Mozilla's implementation of NodeIterator in which a malicious NodeFilter could be created which would detach nodes from the DOM tree while it was being traversed. The use of a detached and subsequently deleted node could result in the execution of attacker-controlled memory.

MFSA 2010-37 / CVE-2010-1214: Security researcher J23 reported via TippingPoint's Zero Day Initiative an error in the code used to store the names and values of plugin parameter elements. A malicious page could embed plugin content containing a very large number of parameter elements which would cause an overflow in the integer value counting them. This integer is later used in allocating a memory buffer used to store the plugin parameters. Under such conditions, too small a buffer would be created and attacker-controlled data could be written past the end of the buffer, potentially resulting in code execution.

MFSA 2010-39 / CVE-2010-2752: Security researcher J23 reported via TippingPoint's Zero Day Initiative that an array class used to store CSS values contained an integer overflow vulnerability. The 16 bit integer value used in allocating the size of the array could overflow, resulting in too small a memory buffer being created. When the array was later populated with CSS values data would be written past the end of the buffer potentially resulting in the execution of attacker-controlled memory.

MFSA 2010-40 / CVE-2010-2753: Security researcher regenrecht reported via TippingPoint's Zero Day Initiative an integer overflow vulnerability in the implementation of the XUL <tree> element's selection attribute. When the size of a new selection is sufficiently large the integer used in calculating the length of the selection can overflow, resulting in a bogus range being marked selected. When adjustSelection is then called on the bogus range the range is deleted leaving dangling references to the ranges which could be used by an attacker to call into deleted memory and run arbitrary code on a victim's computer.

MFSA 2010-41 / CVE-2010-1205: OUSPG researcher Aki Helin reported a buffer overflow in Mozilla graphics code which consumes image data processed by libpng. A malformed PNG file could be created which would cause libpng to incorrectly report the size of the image to downstream consumers. When the dimensions of such images are underreported, the Mozilla code responsible for displaying the graphic will allocate too small a memory buffer to contain the image data and will wind up writing data past the end of the buffer. This could result in the execution of attacker-controlled memory.

MFSA 2011-42 / CVE-2010-1213: Security researcher Yosuke Hasegawa reported that the Web Worker method importScripts can read and parse resources from other domains even when the content is not valid JavaScript. This is a violation of the same-origin policy and could be used by an attacker to steal information from other sites.

MFSA 2010-45 / CVE-2010-1206: Google security researcher Michal Zalewski reported two methods for spoofing the contents of the location bar. The first method works by opening a new window containing a resource that responds with an HTTP 204 (no content) and then using the reference to the new window to insert HTML content into the blank document. The second location bar spoofing method does not require that the resource opened in a new window respond with 204, as long as the opener calls window.stop() before the document is loaded.
In either case a user could be mislead as to the correct location of the document they are currently viewing.

MFSA 2010-45 / CVE-2010-2751: Security researcher Jordi Chancel reported that the location bar could be spoofed to look like a secure page when the current document was served via plaintext. The vulnerability is triggered by a server by first redirecting a request for a plaintext resource to another resource behind a valid SSL/TLS certificate. A second request made to the original plaintext resource which is responded to not with a redirect but with JavaScript containing history.back() and history.forward() will result in the plaintext resource being displayed with valid SSL/TLS badging in the location bar. References

MFSA 2010-46 / CVE-2010-0654: Google security researcher Chris Evans reported that data can be read across domains by injecting bogus CSS selectors into a target site and then retrieving the data using JavaScript APIs. If an attacker can inject opening and closing portions of a CSS selector into points A and B of a target page, then the region between the two injection points becomes readable to JavaScript through, for example, the getComputedStyle() API.

MFSA 2010-47 / CVE-2010-2754: Security researcher Soroush Dalili reported that potentially sensitive URL parameters could be leaked across domains upon script errors when the script filename and line number is included in the error message.

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

The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

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 with the privileges of the user running SeaMonkey. (CVE-2010-1211, CVE-2010-2753, CVE-2010-1214)

A memory corruption flaw was found in the way SeaMonkey decoded certain PNG images. An attacker could create a specially crafted PNG image that, when opened, could cause SeaMonkey to crash or, potentially, execute arbitrary code with the privileges of the user running SeaMonkey. (CVE-2010-1205)

A same-origin policy bypass flaw was found in SeaMonkey. An attacker could create a malicious web page that, when viewed by a victim, could steal private data from a different website the victim has loaded with SeaMonkey. (CVE-2010-2754)

A flaw was found in the way SeaMonkey displayed the location bar when visiting a secure web page. A malicious server could use this flaw to present data that appears to originate from a secure server, even though it does not. (CVE-2010-2751)

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

This update brings Mozilla Firefox to the 3.5.11 security release.

It fixes following security issues :

  - Several memory safety bugs in habe been identified in     the browser engine used in Firefox and other     Mozilla-based products. Some of these bugs show evidence     of memory corruption under certain circumstances, and it     is presumed that with enough effort at least some of     these could be exploited to run arbitrary code. . (MFSA     2010-34 / CVE-2010-1211)

  - An error in the DOM attribute cloning routine has been     reported, where under certain circumstances an event     attribute node can be deleted while another object still     contains a reference to it. This reference could     subsequently be accessed, potentially causing the     execution of attacker controlled memory. . (MFSA 2010-35     / CVE-2010-1208)

  - An error in Mozilla's implementation of NodeIterator has     been reported which can be used to create a malicious     NodeFilter to detach nodes from the DOM tree while it is     being traversed. The use of a detached and subsequently     deleted node could result in the execution of attacker     controlled memory. . (MFSA 2010-36 / CVE-2010-1209)

  - An error in the code used to store the names and values     of plugin parameter elements has been found. A malicious     page could embed plugin content containing a very large     number of parameter elements which would cause an     overflow in the integer value counting them. This     integer is later used for allocation of a memory buffer     to store the plugin parameters. Under such conditions, a     buffer that is too small would be created and attacker     controlled data could be written past the end of the     buffer, potentially resulting in code execution. . (MFSA     2010-37 / CVE-2010-1214)

  - An array class used to store CSS values contains an     integer overflow vulnerability. A 16 bit integer used to     allocate the memory for the array could overflow,     resulting in too small a buffer being created. When the     array is later populated with CSS values, data could be     written past the end of the buffer, potentially     resulting in the execution of attacker controlled     memory. . (MFSA 2010-39 / CVE-2010-2752)

  - An integer overflow vulnerability in the implementation     of the XUL <tree> element's selection attribute has been     found. When the size of a new selection is sufficiently     large, the integer used in calculating the length of the     selection can overflow, resulting in a bogus range being     marked as selected. When adjustSelection is then called     on the bogus range, the range is deleted, leaving     dangling references to the ranges. These could be used     by an attacker to call into deleted memory and run     arbitrary code on a victim's computer. . (MFSA 2010-40 /     CVE-2010-2753)

  - A buffer overflow in Mozilla graphics code which     consumes image data processed by libpng has been     reported. A malformed PNG file could be created causing     libpng to report an incorrect size of the image. When     the dimensions of such images are underreported, the     Mozilla code displaying the graphic will allocate a     memory buffer to small to contain the image data and     will wind up writing data past the end of the buffer.
    This could result in the execution of     attacker-controlled memory. . (MFSA 2010-41 /     CVE-2010-1205)

  - The Web Worker method importScripts can read and parse     resources from other domains even when the content is     not valid JavaScript. This is a violation of the     same-origin policy and could be used by an attacker to     steal information from other sites. . (MFSA 2010-42 /     CVE-2010-1213)

  - Two methods for spoofing the content of the location bar     have been reported. The first method works by opening a     new window containing a resource that responds with an     HTTP 204 (no content) and then using the reference to     the new window to insert HTML content into the blank     document. The second location bar spoofing method does     not require that the resource opened in a new window     respond with 204, as long as the opener calls     window.stop() before the document is loaded. In either     case a user could be mislead about the correct location     of the document they are currently viewing. . (MFSA     2010-45 / CVE-2010-1206)

  - The location bar can be spoofed to look like a secure     page even though the current document was served via     plaintext. The vulnerability is triggered by a server by     first redirecting a request for a plaintext resource to     another resource behind a valid SSL/TLS certificate. A     second request made to the original plaintext resource     which is responded to not with a redirect, but with     JavaScript calling history.back() and history.forward()     will result in the plaintext resource being displayed     with a valid SSL/TLS badge in the location bar. . (MFSA     2010-45 / CVE-2010-2751)

  - Data can be read across domains by injecting bogus CSS     selectors into a target site and then retrieving the     data using JavaScript APIs. If an attacker can inject     opening and closing portions of a CSS selector into     points A and B of a target page, then the region between     the two injection points becomes readable to JavaScript     through, for example, the getComputedStyle() API. .
    (MFSA 2010-46 / CVE-2010-0654)

  - Potentially sensitive URL parameters can be leaked     across domains upon script errors when the script     filename and line number is included in the error     message. . (MFSA 2010-47 / CVE-2010-2754)

The Mozilla Project reports :

MFSA 2010-34 Miscellaneous memory safety hazards (rv:1.9.2.7/ 1.9.1.11)

MFSA 2010-35 DOM attribute cloning remote code execution vulnerability

MFSA 2010-36 Use-after-free error in NodeIterator

MFSA 2010-37 Plugin parameter EnsureCachedAttrParamArrays remote code execution vulnerability

MFSA 2010-38 Arbitrary code execution using SJOW and fast native function

MFSA 2010-39 nsCSSValue::Array index integer overflow

MFSA 2010-40 nsTreeSelection dangling pointer remote code execution vulnerability

MFSA 2010-41 Remote code execution using malformed PNG image

MFSA 2010-42 Cross-origin data disclosure via Web Workers and importScripts

MFSA 2010-43 Same-origin bypass using canvas context

MFSA 2010-44 Characters mapped to U+FFFD in 8 bit encodings cause subsequent character to vanish

MFSA 2010-45 Multiple location bar spoofing vulnerabilities

MFSA 2010-46 Cross-domain data theft using CSS

MFSA 2010-47 Cross-origin data leakage from script filename in error messages

Update to new upstream SeaMonkey version 2.0.6, fixing multiple security issues detailed in the upstream advisories:
http://www.mozilla.org/security/known- vulnerabilities/seamonkey20.html#seamonkey2.0.6

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

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 with the privileges of the user running Firefox. (CVE-2010-1208, CVE-2010-1209, CVE-2010-1211, CVE-2010-1212, CVE-2010-1214, CVE-2010-1215, CVE-2010-2752, CVE-2010-2753)

A memory corruption flaw was found in the way Firefox decoded certain PNG images. An attacker could create a specially crafted PNG image that, when opened, could cause Firefox to crash or, potentially, execute arbitrary code with the privileges of the user running Firefox. (CVE-2010-1205)

Several same-origin policy bypass flaws were found in Firefox. An attacker could create a malicious web page that, when viewed by a victim, could steal private data from a different website the victim has loaded with Firefox. (CVE-2010-0654, CVE-2010-1207, CVE-2010-1213, CVE-2010-2754)

A flaw was found in the way Firefox presented the location bar to a user. A malicious website could trick a user into thinking they are visiting the site reported by the location bar, when the page is actually content controlled by an attacker. (CVE-2010-1206)

A flaw was found in the way Firefox displayed the location bar when visiting a secure web page. A malicious server could use this flaw to present data that appears to originate from a secure server, even though it does not. (CVE-2010-2751)

A flaw was found in the way Firefox displayed certain malformed characters. A malicious web page could use this flaw to bypass certain string sanitization methods, allowing it to display malicious information to users. (CVE-2010-1210)

For technical details regarding these flaws, refer to the Mozilla security advisories for Firefox 3.6.7.

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

A memory corruption flaw was found in the way Thunderbird decoded certain PNG images. An attacker could create a mail message containing a specially crafted PNG image that, when opened, could cause Thunderbird to crash or, potentially, execute arbitrary code with the privileges of the user running Thunderbird. (CVE-2010-1205)

Several flaws were found in the processing of malformed HTML mail content. An HTML mail message containing malicious content could cause Thunderbird to crash or, potentially, execute arbitrary code with the privileges of the user running Thunderbird. (CVE-2010-0174, CVE-2010-1200, CVE-2010-1211, CVE-2010-1214, CVE-2010-2753)

An integer overflow flaw was found in the processing of malformed HTML mail content. An HTML mail message containing malicious content could cause Thunderbird to crash or, potentially, execute arbitrary code with the privileges of the user running Thunderbird. (CVE-2010-1199)

Several use-after-free flaws were found in Thunderbird. Viewing an HTML mail message containing malicious content could result in Thunderbird executing arbitrary code with the privileges of the user running Thunderbird. (CVE-2010-0175, CVE-2010-0176, CVE-2010-0177)

A flaw was found in the way Thunderbird plug-ins interact. It was possible for a plug-in to reference the freed memory from a different plug-in, resulting in the execution of arbitrary code with the privileges of the user running Thunderbird. (CVE-2010-1198)

A flaw was found in the way Thunderbird handled the 'Content-Disposition: attachment' HTTP header when the 'Content-Type:
multipart' HTTP header was also present. Loading remote HTTP content that allows arbitrary uploads and relies on the 'Content-Disposition:
attachment' HTTP header to prevent content from being displayed inline, could be used by an attacker to serve malicious content to users. (CVE-2010-1197)

A same-origin policy bypass flaw was found in Thunderbird. Remote HTML content could steal private data from different remote HTML content Thunderbird has loaded. (CVE-2010-2754)

All running instances of Thunderbird must be restarted for the update to take effect.

From Red Hat Security Advisory 2010:0546 :

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

The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

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 with the privileges of the user running SeaMonkey. (CVE-2010-1211, CVE-2010-2753, CVE-2010-1214)

A memory corruption flaw was found in the way SeaMonkey decoded certain PNG images. An attacker could create a specially crafted PNG image that, when opened, could cause SeaMonkey to crash or, potentially, execute arbitrary code with the privileges of the user running SeaMonkey. (CVE-2010-1205)

A same-origin policy bypass flaw was found in SeaMonkey. An attacker could create a malicious web page that, when viewed by a victim, could steal private data from a different website the victim has loaded with SeaMonkey. (CVE-2010-2754)

A flaw was found in the way SeaMonkey displayed the location bar when visiting a secure web page. A malicious server could use this flaw to present data that appears to originate from a secure server, even though it does not. (CVE-2010-2751)

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

ID	名前	製品	ファミリー	公開日	更新日	深刻度
47854	openSUSE Security Update : seamonkey (openSUSE-SU-2010:0430-1)	Nessus	SuSE Local Security Checks	2010/7/27	2021/1/14	high
47880	RHEL 3 / 4 : seamonkey (RHSA-2010:0546)	Nessus	Red Hat Local Security Checks	2010/7/28	2021/1/14	high
49894	SuSE 10 Security Update : Mozilla Firefox (ZYPP Patch Number 7101)	Nessus	SuSE Local Security Checks	2010/10/11	2021/1/14	high
47794	FreeBSD : mozilla -- multiple vulnerabilities (8c2ea875-9499-11df-8e32-000f20797ede)	Nessus	FreeBSD Local Security Checks	2010/7/22	2021/1/6	high
47807	Fedora 13 : seamonkey-2.0.6-1.fc13 (2010-11327)	Nessus	Fedora Local Security Checks	2010/7/23	2021/1/11	high
60818	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	high
60822	Scientific Linux Security Update : thunderbird on SL5.x i386/x86_64	Nessus	Scientific Linux Local Security Checks	2012/8/1	2021/1/14	critical
68067	Oracle Linux 3 / 4 : seamonkey (ELSA-2010-0546)	Nessus	Oracle Linux Local Security Checks	2013/7/12	2021/1/14	high

検出

プラグインの検索

high

high

high

high

high

high

critical

high