This script is Copyright (C) 2007-2013 Tenable Network Security, Inc.
The remote SuSE system is missing the security patch seamonkey-1952
This security update brings Mozilla Seamonkey to version
Please also see
es.html for more details.
It includes fixes to the following security problems:
- CVE-2006-3801/MFSA 2006-44: Code execution through
deleted frame reference
Thilo Girmann discovered that in certain circumstances a
cleared when the referenced content went away, and he
demonstrated that this pointer to a deleted object could be
used to execute native code supplied by the attacker.
An anonymous researcher for TippingPoint and the Zero Day
Initiative showed that when used in a web page Java would
reference properties of the window.navigator object as it
started up. If the page replaced the navigator object
before starting Java then the browser would crash in a way
that could be exploited to run native code supplied by the
- CVE-2006-3113/MFSA 2006-46: Memory corruption with
Secunia Research has discovered a vulnerability in
Mozilla Firefox 1.5 branch, which can be exploited by
malicious people to compromise a user's system.
The vulnerability is caused due to an memory corruption
error within the handling of simultaneously happening XPCOM
events, which leads to use of a deleted timer object. This
generally results in a crash but potentially could be
exploited to execute arbitrary code on a user's system when
a malicious website is visited.
- CVE-2006-3802/MFSA 2006-47: Native DOM methods can be
hijacked across domains
A malicious page can hijack native DOM methods on a
document object in another domain, which will run the
attacker's script when called by the victim page. This
could be used to steal login cookies, password, or other
sensitive data on the target page, or to perform actions on
behalf of a logged-in user.
Access checks on all other properties and document nodes
are performed correctly. This cross-site scripting (XSS)
attack is limited to pages which use standard DOM methods
of the top-level document object, such as
document.getElementById(). This includes many popular
sites, especially the newer ones that offer rich
interaction to the user.
H. D. Moore reported a testcase that was able to trigger
deleted a temporary variable still being used in the
creation of a new Function object. The resulting use of a
deleted object may be potentially exploitable to run native
code provided by the attacker.
- CVE-2006-3804/MFSA 2006-49: Heap buffer overwrite on
A VCard attachment with a malformed base64 field (such as
a photo) can trigger a heap buffer overwrite. These have
proven exploitable in the past, though in this case the
overwrite is accompanied by an integer underflow that would
attempt to copy more data than the typical machine has,
leading to a crash.
Mozilla developers found and fixed several potential
Igor Bukanov and shutdown found additional places where
an untimely garbage collection could delete a temporary
object that was in active use (similar to MFSA 2006-01 and
MFSA 2006-10). Some of these may allow an attacker to run
arbitrary code given the right conditions.
Georgi Guninski found potential integer overflow issues
with long strings in the toSource() methods of the Object,
Array and String objects as well as string function
- CVE-2006-3807/MFSA 2006-51: Privilege escalation using
named-functions and redefined 'new Object()'
have a parent object created using the standard Object()
constructor (ECMA-specified behavior) and that this
constructor can be redefined by script (also ECMA-specified
behavior). If the Object() constructor is changed to return
a reference to a privileged object with useful properties
it is possible to have attacker-supplied script excuted
with elevated privileges by calling the function. This
could be used to install malware or take other malicious
Our fix involves calling the internal Object constructor
which appears to be what other ECMA-compatible interpreters
- CVE-2006-3808/MFSA 2006-52: PAC privilege escalation
moz_bug_r_a4 reports that a malicious Proxy AutoConfig
(PAC) server could serve a PAC script that can execute code
with elevated privileges by setting the required
FindProxyForURL function to the eval method on a privileged
object that leaked into the PAC sandbox. By redirecting the
victim to a specially-crafted URL -- easily done since the
PAC script controls which proxy to use -- the URL
'hostname' can be executed as privileged script.
A malicious proxy server can perform spoofing attacks on
the user so it was already important to use a trustworthy
- CVE-2006-3809/MFSA 2006-53: UniversalBrowserRead
shutdown reports that scripts granted the
UniversalBrowserRead privilege can leverage that into the
equivalent of the far more powerful UniversalXPConnect
since they are allowed to 'read' into a privileged context.
This allows the attacker the ability to run scripts with
the full privelege of the user running the browser,
possibly installing malware or snooping on private data.
This has been fixed so that UniversalBrowserRead and
UniversalBrowserWrite are limited to reading from and
writing into only normally-privileged browser windows and
- CVE-2006-3810/MFSA 2006-54: XSS with
shutdown reports that cross-site scripting (XSS) attacks
could be performed using the construct
XPCNativeWrapper(window).Function(...), which created a
function that appeared to belong to the window in question
even after it had been navigated to the target site.
- CVE-2006-3811/MFSA 2006-55: Crashes with evidence of
As part of the Firefox 18.104.22.168 stability and security
release, developers in the Mozilla community looked for and
fixed several crash bugs to improve the stability of
Mozilla clients. Some of these crashes showed evidence of
memory corruption that we presume could be exploited to run
arbitrary code with enough effort.
- CVE-2006-3812/MFSA 2006-56: chrome: scheme loading remote
Benjamin Smedberg discovered that chrome URL's could be
made to reference remote files, which would run scripts
with full privilege. There is no known way for web content
to successfully load a chrome: url, but if a user could be
convinced to do so manually (perhaps by copying a link and
pasting it into the location bar) this could be exploited.
Install the seamonkey-1952 security patch by using 'yast', for example.
Risk factor :
High / CVSS Base Score : 7.5
Public Exploit Available : true