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.

The remote host is affected by the vulnerability described in GLSA-201301-01 (Mozilla Products: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in Mozilla Firefox,       Thunderbird, SeaMonkey, NSS, GNU IceCat, and XULRunner. Please review the       CVE identifiers referenced below for details.
  Impact :

    A remote attacker could entice a user to view a specially crafted web       page or email, possibly resulting in execution of arbitrary code or a       Denial of Service condition. Furthermore, a remote attacker may be able       to perform Man-in-the-Middle attacks, obtain sensitive information,       bypass restrictions and protection mechanisms, force file downloads,       conduct XML injection attacks, conduct XSS attacks, bypass the Same       Origin Policy, spoof URL&rsquo;s for phishing attacks, trigger a vertical       scroll, spoof the location bar, spoof an SSL indicator, modify the       browser&rsquo;s font, conduct clickjacking attacks, or have other unspecified       impact.
    A local attacker could gain escalated privileges, obtain sensitive       information, or replace an arbitrary downloaded file.
  Workaround :

    There is no known workaround at this time.

This update brings Mozilla Firefox to the 3.6.8 security release.

It fixes following security bugs: MFSA 2010-34 / CVE-2010-1211 / CVE-2010-1212: 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.

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-38 / CVE-2010-1215: Mozilla security researcher moz_bug_r_a4 reported that when content script which is running in a chrome context accesses a content object via SJOW, the content code can gain access to an object from the chrome scope and use that object to run arbitrary JavaScript with chrome privileges.

Firefox 3.5 and other Mozilla products built from Gecko 1.9.1 were not affected by this issue.

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 2010-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-43 / CVE-2010-1207: Mozilla developer Vladimir Vukicevic reported that a canvas element can be used to read data from another site, violating the same-origin policy. The read restriction placed on a canvas element which has had cross-origin data rendered into it can be bypassed by retaining a reference to the canvas element's context and deleting the associated canvas node from the DOM.

MFSA 2010-44 / CVE-2010-1210: Security researcher O. Andersen reported that undefined positions within various 8 bit character encodings are mapped to the sequence U+FFFD which when displayed causes the immediately following character to disappear from the text run. This could potentially contribute to XSS problems on sites which expected extra characters to be present within strings being sanitized on the server.

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.

MFSA 2010-48 / CVE-2010-2755: Mozilla developer Daniel Holbert reported that the fix to the plugin parameter array crash that was fixed in Firefox 3.6.7 caused a crash showing signs of memory corruption. In certain circumstances, properties in the plugin instance's parameter array could be freed prematurely leaving a dangling pointer that the plugin could execute, potentially calling into attacker-controlled memory.

Versions of Firefox 3.6.x prior to 3.6.7 are potentially affected by multiple vulnerabilities :

 - Multiple memory safety bugs could result in memory corruption, potentially resulting in arbitrary code execution. (MFSA 2010-34)
 - An error in DOM attribute cloning could result in arbitrary code execution. (MFSA 2010-35)
 - An error in Mozilla's 'NodeIterator' implementation could lead to arbitrary code execution. (MFSA 2010-36)
 - An error in the code to store the names and values of plugin parameters could lead to arbitrary code execution. (MFSA 2010-37)
 - It may be possible to run arbitrary JavaScript with chrome privileges using SJOW and fast native function. (MFSA 2010-38)
 - The array class used to store CSS values is affected by an integer overflow vulnerability. (MFSA 2010-39)
 - An integer overflow vulnerability exists in the 'selection' attribute of the XUL tree element. (MFSA 2010-40)
 - A buffer overflow exists in Mozilla graphics code could lead to arbitrary code execution. (MFSA 2010-41)
 - It is possible to read and parse resources from other domains even when the content is not valid javascript leading to cross-domain data disclosure. (MFSA 2010-42)
 - The canvas element can be used to read data from another site leading to a same-origin bypass vulnerability. (MFSA 2010-43)
 - Characters mapped to U+FFFD in 8 bit encodings cause subsequent characteres to dissapear, potentially contributing to cross-site scripting issues on certain websites. (MFSA 2010-44)
 - Multiple location bar spoofing vulnerabilities exist. (MFSA 2010-45)
 - It is possible to read data across domains by injecting bogus CSS selectors into a target site. (MFSA 2010-46)
 - Potentially sensitive URL parameters could be leaked across domains via script errors. (MFSA 2010-47)

Versions of Mozilla Thunderbird 3.1.x prior to 3.1.1 are affected by the following vulnerabilities :

 - Multiple memory safety bugs could result in memory corruption, potentially resulting in arbitrary code execution. (MFSA 2010-34)
 - It may be possible to run arbitrary JavaScript with chrome privileges using SJOW and fast native function. (MFSA 2010-38)
 - The array class used to store CSS values is affected by an integer overflow vulnerability. (MFSA 2010-39)
 - An integer overflow vulnerability exists in the 'selection' attribute of the XUL tree element. (MFSA 2010-40)
 - A buffer overflow exists in Mozilla graphics code could lead to arbitrary code execution. (MFSA 2010-41)
 - It is possible to read and parse resources from other domains even when the content is not valid javascript leading to cross-domain data disclosure. (MFSA 2010-42)
 - The canvas element can be used to read data from another site leading to a same-origin bypass vulnerability. (MFSA 2010-43)
 - Characters mapped to U+FFFD in 8-bit encodings cause subsequent characteres to dissapear, potentially contributing to cross-site scripting issues on certain websites. (MFSA 2010-44)
 - It is possible to read data across domains by injecting bogus CSS selectors into a target site. (MFSA 2010-46)
 - Potentially sensitive URL parameters could be leaked across domains via script errors. (MFSA 2010-47)

Versions of Firefox 3.6.x earlier than 3.6.7 are potentially affected by multiple vulnerabilities :

  Multiple memory safety bugs could result in memory corruption, potentially resulting in arbitrary code execution. (MFSA 2010-34)

  - An error in DOM attribute cloning could result in arbitrary code execution. (MFSA 2010-35)

  - An error in Mozilla's 'NodeIterator' implementation could lead to arbitrary code execution. (MFSA 2010-36)

  An error in the code to store the names and values of plugin parameters could lead to arbitrary code execution. (MFSA 2010-37)

  - It may be possible to run arbitrary JavaScript with chrome privileges using SJOW and fast native function. (MFSA 2010-38)

  - The array class used to store CSS values is affected by an integer overflow vulnerability. (MFSA 2010-39)

  - An integer overflow vulnerability exists in the 'selection' attribute of the XUL tree element. (MFSA 2010-40)

  - A buffer overflow exists in Mozilla graphics code could lead to arbitrary code execution. (MFSA 2010-41)

  - It is possible to read and parse resources from other domains even when the content is not valid javascript leading to cross-domain data disclosure. (MFSA 2010-42)

  - The canvas element can be used to read data from another site leading to a same-origin bypass vulnerability. (MFSA 2010-43)

  - Characters mapped to U+FFFD in 8 bit encodings cause subsequent characteres to dissapear, potentially contributing to cross-site scripting issues on certain websites. (MFSA 2010-44)

  - Multiple location bar spoofing vulnerabilities exist. (MFSA 2010-45)

  - It is possible to read data across domains by injecting bogus CSS selectors into a target site. (MFSA 2010-46)

  - Potentially sensitive URL parameters could be leaked across domains via script errors. (MFSA 2010-47)

ID	名前	製品	ファミリー	公開日	更新日	深刻度
48342	CentOS 3 : seamonkey (CESA-2010:0546)	Nessus	CentOS Local Security Checks	2010/8/17	2021/1/4	high
63402	GLSA-201301-01 : Mozilla Products: Multiple vulnerabilities (BEAST)	Nessus	Gentoo Local Security Checks	2013/1/8	2022/12/5	critical
75646	openSUSE Security Update : MozillaFirefox (MozillaFirefox-2807)	Nessus	SuSE Local Security Checks	2014/6/13	2021/1/14	critical
5607	Mozilla Firefox 3.6.x < 3.6.7 Multiple Vulnerabilities	Nessus Network Monitor	Web Clients	2010/7/21	2019/3/6	medium
5609	Mozilla Thunderbird 3.1.x < 3.1.1 Multiple Vulnerabilities	Nessus Network Monitor	SMTP Clients	2010/7/21	2019/3/6	medium
800780	Firefox 3.6.x < 3.6.7 Multiple Vulnerabilities	Log Correlation Engine	Web Clients	2010/7/21		high

検出

プラグインの検索

high

critical

critical

medium

medium

high