The Mozilla Project reports :

MFSA 2010-74 Miscellaneous memory safety hazards (rv:1.9.2.13/ 1.9.1.16)

MFSA 2010-75 Buffer overflow while line breaking after document.write with long string

MFSA 2010-76 Chrome privilege escalation with window.open and isindex element

MFSA 2010-77 Crash and remote code execution using HTML tags inside a XUL tree

MFSA 2010-78 Add support for OTS font sanitizer

MFSA 2010-79 Java security bypass from LiveConnect loaded via data:
URL meta refresh

MFSA 2010-80 Use-after-free error with nsDOMAttribute MutationObserver

MFSA 2010-81 Integer overflow vulnerability in NewIdArray

MFSA 2010-82 Incomplete fix for CVE-2010-0179

MFSA 2010-83 Location bar SSL spoofing using network error page

MFSA 2010-84 XSS hazard in multiple character encodings

Mozilla Firefox 3.5 was updated to update 3.5.16 fixing several security issues.

  - 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-74)

    Jesee Ruderman, Andreas Gal, Nils, and Brian Hackett     reported memory safety problems that affected Firefox     3.6 and Firefox 3.5. (CVE-2010-3776)

    Igor Bukanov reported a memory safety problem that was     fixed in Firefox 3.6 only. (CVE-2010-3777)

    Jesse Ruderman reported a crash which affected Firefox     3.5 only. (CVE-2010-3778)

  - Dirk Heinrich reported that on Windows platforms when     document.write() was called with a very long string a     buffer overflow was caused in line breaking routines     attempting to process the string for display. Such cases     triggered an invalid read past the end of an array     causing a crash which an attacker could potentially use     to run arbitrary code on a victim's computer. (MFSA     2010-75 / CVE-2010-3769)

  - Security researcher echo reported that a web page could     open a window with an about:blank location and then     inject an. (MFSA 2010-76 / CVE-2010-3771)

    element into that page which upon submission would     redirect to a chrome: document. The effect of this     defect was that the original page would wind up with a     reference to a chrome-privileged object, the opened     window, which could be leveraged for privilege     escalation attacks.

    Mozilla security researcher moz_bug_r_a4 provided     proof-of-concept code demonstrating how the above     vulnerability could be used to run arbitrary code with     chrome privileges.

  - Security researcher wushi of team509 reported that when     a XUL tree had an HTML. (MFSA 2010-77 / CVE-2010-3772)

    element nested inside a element then code attempting to     display content in the XUL tree would incorrectly treat     the element as a parent node to tree content underneath     it resulting in incorrect indexes being calculated for     the child content. These incorrect indexes were used in     subsequent array operations which resulted in writing     data past the end of an allocated buffer. An attacker     could use this issue to crash a victim's browser and run     arbitrary code on their machine.

  - Mozilla added the OTS font sanitizing library to prevent     downloadable fonts from exposing vulnerabilities in the     underlying OS font code. This library mitigates against     several issues independently reported by Red Hat     Security Response Team member Marc Schoenefeld and     Mozilla security researcher Christoph Diehl. (MFSA     2010-78 / CVE-2010-3768)

  - Security researcher Gregory Fleischer reported that when     a Java LiveConnect script was loaded via a data: URL     which redirects via a meta refresh, then the resulting     plugin object was created with the wrong security     principal and thus received elevated privileges such as     the abilities to read local files, launch processes, and     create network connections. (MFSA 2010-79 /     CVE-2010-3775)

  - Security researcher regenrecht reported via     TippingPoint's Zero Day Initiative that a nsDOMAttribute     node can be modified without informing the iterator     object responsible for various DOM traversals. This flaw     could lead to a inconsistent state where the iterator     points to an object it believes is part of the DOM but     actually points to some other object. If such an object     had been deleted and its memory reclaimed by the system,     then the iterator could be used to call into     attacker-controlled memory. (MFSA 2010-80 /     CVE-2010-3766)

  - Security researcher regenrecht reported via     TippingPoint's Zero Day Initiative that JavaScript     arrays were vulnerable to an integer overflow     vulnerability. The report demonstrated that an array     could be constructed containing a very large number of     items such that when memory was allocated to store the     array items, the integer value used to calculate the     buffer size would overflow resulting in too small a     buffer being allocated. Subsequent use of the array     object could then result in data being written past the     end of the buffer and causing memory corruption. (MFSA     2010-81 / CVE-2010-3767)

  - Mozilla security researcher moz_bug_r_a4 reported that     the fix for CVE-2010-0179 could be circumvented     permitting the execution of arbitrary JavaScript with     chrome privileges. (MFSA 2010-82 / CVE-2010-3773)

  - Google security researcher Michal Zalewski reported that     when a window was opened to a site resulting in a     network or certificate error page, the opening site     could access the document inside the opened window and     inject arbitrary content. An attacker could use this bug     to spoof the location bar and trick a user into thinking     they were on a different site than they actually were.
    (MFSA 2010-83 / CVE-2010-3774)

  - Security researchers Yosuke Hasegawa and Masatoshi     Kimura reported that the x-mac-arabic, x-mac-farsi and     x-mac-hebrew character encodings are vulnerable to XSS     attacks due to some characters being converted to angle     brackets when displayed by the rendering engine. Sites     using these character encodings would thus be     potentially vulnerable to script injection attacks if     their script filtering code fails to strip out these     specific characters. (MFSA 2010-84 / CVE-2010-3770)

Mozilla SeaMonkey 2.0 was updated to update 2.0.11 fixing several security issues.

MFSA 2010-74: 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.

Jesee Ruderman, Andreas Gal, Nils, and Brian Hackett reported memory safety problems that affected Firefox 3.6 and Firefox 3.5.
(CVE-2010-3776) Igor Bukanov reported a memory safety problem that was fixed in Firefox 3.6 only. (CVE-2010-3777) Jesse Ruderman reported a crash which affected Firefox 3.5 only. (CVE-2010-3778)

MFSA 2010-75 / CVE-2010-3769: Dirk Heinrich reported that on Windows platforms when document.write() was called with a very long string a buffer overflow was caused in line breaking routines attempting to process the string for display. Such cases triggered an invalid read past the end of an array causing a crash which an attacker could potentially use to run arbitrary code on a victim's computer.

MFSA 2010-76 / CVE-2010-3771: Security researcher echo reported that a web page could open a window with an about:blank location and then inject an <isindex> element into that page which upon submission would redirect to a chrome: document. The effect of this defect was that the original page would wind up with a reference to a chrome-privileged object, the opened window, which could be leveraged for privilege escalation attacks.

Mozilla security researcher moz_bug_r_a4 provided proof-of-concept code demonstrating how the above vulnerability could be used to run arbitrary code with chrome privileges.

MFSA 2010-77 / CVE-2010-3772: Security researcher wushi of team509 reported that when a XUL tree had an HTML <div> element nested inside a <treechildren> element then code attempting to display content in the XUL tree would incorrectly treat the <div> element as a parent node to tree content underneath it resulting in incorrect indexes being calculated for the child content. These incorrect indexes were used in subsequent array operations which resulted in writing data past the end of an allocated buffer. An attacker could use this issue to crash a victim's browser and run arbitrary code on their machine.

MFSA 2010-78 / CVE-2010-3768: Mozilla added the OTS font sanitizing library to prevent downloadable fonts from exposing vulnerabilities in the underlying OS font code. This library mitigates against several issues independently reported by Red Hat Security Response Team member Marc Schoenefeld and Mozilla security researcher Christoph Diehl.

MFSA 2010-79 / CVE-2010-3775: Security researcher Gregory Fleischer reported that when a Java LiveConnect script was loaded via a data:
URL which redirects via a meta refresh, then the resulting plugin object was created with the wrong security principal and thus received elevated privileges such as the abilities to read local files, launch processes, and create network connections.

MFSA 2010-80 / CVE-2010-3766: Security researcher regenrecht reported via TippingPoint's Zero Day Initiative that a nsDOMAttribute node can be modified without informing the iterator object responsible for various DOM traversals. This flaw could lead to a inconsistent state where the iterator points to an object it believes is part of the DOM but actually points to some other object. If such an object had been deleted and its memory reclaimed by the system, then the iterator could be used to call into attacker-controlled memory.

MFSA 2010-81 / CVE-2010-3767: Security researcher regenrecht reported via TippingPoint's Zero Day Initiative that JavaScript arrays were vulnerable to an integer overflow vulnerability. The report demonstrated that an array could be constructed containing a very large number of items such that when memory was allocated to store the array items, the integer value used to calculate the buffer size would overflow resulting in too small a buffer being allocated. Subsequent use of the array object could then result in data being written past the end of the buffer and causing memory corruption.

MFSA 2010-82 / CVE-2010-3773: Mozilla security researcher moz_bug_r_a4 reported that the fix for CVE-2010-0179 could be circumvented permitting the execution of arbitrary JavaScript with chrome privileges.

MFSA 2010-83 / CVE-2010-3774: Google security researcher Michal Zalewski reported that when a window was opened to a site resulting in a network or certificate error page, the opening site could access the document inside the opened window and inject arbitrary content. An attacker could use this bug to spoof the location bar and trick a user into thinking they were on a different site than they actually were.

MFSA 2010-84 / CVE-2010-3770: Security researchers Yosuke Hasegawa and Masatoshi Kimura reported that the x-mac-arabic, x-mac-farsi and x-mac-hebrew character encodings are vulnerable to XSS attacks due to some characters being converted to angle brackets when displayed by the rendering engine. Sites using these character encodings would thus be potentially vulnerable to script injection attacks if their script filtering code fails to strip out these specific characters.

Update to new upstream SeaMonkey version 2.0.11, fixing multiple security issues detailed in the upstream advisories :

http://www.mozilla.org/security/known-vulnerabilities/seamonkey20.html #seamonkey2.0.11

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.

Mozilla Thunderbird 3.0 was updated to update 3.0.11 fixing several security issues.

MFSA 2010-74: 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.

Jesee Ruderman, Andreas Gal, Nils, and Brian Hackett reported memory safety problems that affected Firefox 3.6 and Firefox 3.5.
(CVE-2010-3776) Igor Bukanov reported a memory safety problem that was fixed in Firefox 3.6 only. (CVE-2010-3777) Jesse Ruderman reported a crash which affected Firefox 3.5 only. (CVE-2010-3778)

MFSA 2010-75 / CVE-2010-3769: Dirk Heinrich reported that on Windows platforms when document.write() was called with a very long string a buffer overflow was caused in line breaking routines attempting to process the string for display. Such cases triggered an invalid read past the end of an array causing a crash which an attacker could potentially use to run arbitrary code on a victim's computer.

MFSA 2010-76 / CVE-2010-3771: Security researcher echo reported that a web page could open a window with an about:blank location and then inject an <isindex> element into that page which upon submission would redirect to a chrome: document. The effect of this defect was that the original page would wind up with a reference to a chrome-privileged object, the opened window, which could be leveraged for privilege escalation attacks.

Mozilla security researcher moz_bug_r_a4 provided proof-of-concept code demonstrating how the above vulnerability could be used to run arbitrary code with chrome privileges.

MFSA 2010-77 / CVE-2010-3772: Security researcher wushi of team509 reported that when a XUL tree had an HTML <div> element nested inside a <treechildren> element then code attempting to display content in the XUL tree would incorrectly treat the <div> element as a parent node to tree content underneath it resulting in incorrect indexes being calculated for the child content. These incorrect indexes were used in subsequent array operations which resulted in writing data past the end of an allocated buffer. An attacker could use this issue to crash a victim's browser and run arbitrary code on their machine.

MFSA 2010-78 / CVE-2010-3768: Mozilla added the OTS font sanitizing library to prevent downloadable fonts from exposing vulnerabilities in the underlying OS font code. This library mitigates against several issues independently reported by Red Hat Security Response Team member Marc Schoenefeld and Mozilla security researcher Christoph Diehl.

MFSA 2010-79 / CVE-2010-3775: Security researcher Gregory Fleischer reported that when a Java LiveConnect script was loaded via a data:
URL which redirects via a meta refresh, then the resulting plugin object was created with the wrong security principal and thus received elevated privileges such as the abilities to read local files, launch processes, and create network connections.

MFSA 2010-80 / CVE-2010-3766: Security researcher regenrecht reported via TippingPoint's Zero Day Initiative that a nsDOMAttribute node can be modified without informing the iterator object responsible for various DOM traversals. This flaw could lead to a inconsistent state where the iterator points to an object it believes is part of the DOM but actually points to some other object. If such an object had been deleted and its memory reclaimed by the system, then the iterator could be used to call into attacker-controlled memory.

MFSA 2010-81 / CVE-2010-3767: Security researcher regenrecht reported via TippingPoint's Zero Day Initiative that JavaScript arrays were vulnerable to an integer overflow vulnerability. The report demonstrated that an array could be constructed containing a very large number of items such that when memory was allocated to store the array items, the integer value used to calculate the buffer size would overflow resulting in too small a buffer being allocated. Subsequent use of the array object could then result in data being written past the end of the buffer and causing memory corruption.

MFSA 2010-82 / CVE-2010-3773: Mozilla security researcher moz_bug_r_a4 reported that the fix for CVE-2010-0179 could be circumvented permitting the execution of arbitrary JavaScript with chrome privileges.

MFSA 2010-83 / CVE-2010-3774: Google security researcher Michal Zalewski reported that when a window was opened to a site resulting in a network or certificate error page, the opening site could access the document inside the opened window and inject arbitrary content. An attacker could use this bug to spoof the location bar and trick a user into thinking they were on a different site than they actually were.

MFSA 2010-84 / CVE-2010-3770: Security researchers Yosuke Hasegawa and Masatoshi Kimura reported that the x-mac-arabic, x-mac-farsi and x-mac-hebrew character encodings are vulnerable to XSS attacks due to some characters being converted to angle brackets when displayed by the rendering engine. Sites using these character encodings would thus be potentially vulnerable to script injection attacks if their script filtering code fails to strip out these specific characters.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
51132	FreeBSD : mozilla -- multiple vulnerabilities (1d8ff4a2-0445-11e0-8e32-000f20797ede)	Nessus	FreeBSD Local Security Checks	2010/12/12	2021/1/6	high
51411	SuSE 10 Security Update : Mozilla Firefox (ZYPP Patch Number 7280)	Nessus	SuSE Local Security Checks	2011/1/4	2021/1/14	high
53797	openSUSE Security Update : seamonkey (seamonkey-3690)	Nessus	SuSE Local Security Checks	2011/5/5	2021/1/14	high
51361	Fedora 13 : seamonkey-2.0.11-1.fc13 (2010-18890)	Nessus	Fedora Local Security Checks	2010/12/23	2021/1/11	high
53683	openSUSE Security Update : MozillaThunderbird (MozillaThunderbird-3687)	Nessus	SuSE Local Security Checks	2011/5/5	2021/1/14	high

检测

插件搜索

high

high

high

high

high