openSUSE Security Update : seamonkey (seamonkey-3690)

This script is Copyright (C) 2011-2014 Tenable Network Security, Inc.

Synopsis :

The remote openSUSE host is missing a security update.

Description :

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

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.

See also :

Solution :

Update the affected seamonkey packages.

Risk factor :

High / CVSS Base Score : 9.3

Ready to Amp Up Your Nessus Experience?

Get Nessus Professional to scan unlimited IPs, run compliance checks & more

Buy Nessus Professional Now