MDKSA-2005:120-1 : mozilla-firefox

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

Synopsis :

The remote Mandrake host is missing one or more security-related

Description :

A number of vulnerabilities were reported and fixed in Firefox 1.0.5
and Mozilla 1.7.9. The following vulnerabilities have been backported
and patched for this update:

In several places the browser UI did not correctly distinguish
between true user events, such as mouse clicks or keystrokes, and
synthetic events genenerated by web content. The problems ranged from
minor annoyances like switching tabs or entering full-screen mode, to
a variant on MFSA 2005-34 Synthetic events are now prevented from
reaching the browser UI entirely rather than depend on each
potentially spoofed function to protect itself from untrusted events
(MFSA 2005-45; CVE-2005-2260).

Scripts in XBL controls from web content continued to be run even
when Javascript was disabled. By itself this causes no harm, but it
could be combined with most script-based exploits to attack people
running vulnerable versions who thought disabling javascript would
protect them. In the Thunderbird and Mozilla Suite mail clients
Javascript is disabled by default for protection against
denial-of-service attacks and worms; this vulnerability could be used
to bypass that protection (MFSA 2005-46; CVE-2005-2261).

If an attacker can convince a victim to use the 'Set As Wallpaper'
context menu item on a specially crafted image then they can run
arbitary code on the user's computer. The image 'source' must be a
javascript: url containing an eval() statement and such an image
would get the 'broken image' icon, but with CSS it could be made
transparent and placed on top of a real image. The attacker would
have to convince the user to change their desktop background to the
exploit image, and to do so by using the Firefox context menu rather
than first saving the image locally and using the normal mechanism
provided by their operating system. This affects only Firefox 1.0.3
and 1.0.4; earlier versions are unaffected. The implementation of
this feature in the Mozilla Suite is also unaffected (MFSA 2005-47;

The InstallTrigger.install() method for launching an install accepts
a callback function that will be called with the final success or
error status. By forcing a page navigation immediately after calling
the install method this callback function can end up running in the
context of the new page selected by the attacker. This is true even
if the user cancels the unwanted install dialog: cancel is an error
status. This callback script can steal data from the new page such as
cookies or passwords, or perform actions on the user's behalf such as
make a purchase if the user is already logged into the target site.
In Firefox the default settings allow only
to bring up this install dialog. This could only be exploited if
users have added questionable sites to the install whitelist, and if
a malicious site can convince you to install from their site that's a
much more powerful attack vector. In the Mozilla Suite the whitelist
feature is turned off by default, any site can prompt the user to
install software and exploit this vulnerability. The browser has been
fixed to clear any pending callback function when switching to a new
site (MFSA 2005-48; CVE-2005-2263).

Sites can use the _search target to open links in the Firefox
sidebar. A missing security check allows the sidebar to inject data:
urls containing scripts into any page open in the browser. This could
be used to steal cookies, passwords or other sensitive data (MFSA
2005-49; CVE-2005-2264).

When InstallVersion.compareTo() is passed an object rather than a
string it assumed the object was another InstallVersion without
verifying it. When passed a different kind of object the browser
would generally crash with an access violation. shutdown has
demonstrated that different javascript objects can be passed on some
OS versions to get control over the instruction pointer. We assume
this could be developed further to run arbitrary machine code if the
attacker can get exploit code loaded at a predictable address (MFSA
2005-50; CVE-2005-2265).

The original frame-injection spoofing bug was fixed in the Mozilla
Suite 1.7 and Firefox 0.9 releases. This protection was accidentally
bypassed by one of the fixes in the Firefox 1.0.3 and Mozilla Suite
1.7.7 releases (MFSA 2005-51; CVE-2005-1937).

A child frame can call top.focus() even if the framing page comes
from a different origin and has overridden the focus() routine. The
call is made in the context of the child frame. The attacker would
look for a target site with a framed page that makes this call but
doesn't verify that its parent comes from the same site. The attacker
could steal cookies and passwords from the framed page, or take
actions on behalf of a signed-in user. This attack would work only
against sites that use frames in this manner (MFSA 2005-52;

Several media players, for example Flash and QuickTime, support
scripted content with the ability to open URLs in the default
browser. The default behavior for Firefox was to replace the
currently open browser window's content with the externally opened
content. If the external URL was a javascript: url it would run as if
it came from the site that served the previous content, which could
be used to steal sensitive information such as login cookies or
passwords. If the media player content first caused a privileged
chrome: url to load then the subsequent javascript: url could execute
arbitrary code. External javascript: urls will now run in a blank
context regardless of what content it's replacing, and external apps
will no longer be able to load privileged chrome: urls in a browser
window. The -chrome command line option to load chrome applications
is still supported (MFSA 2005-53; CVE-2005-2267).

Alerts and prompts created by scripts in web pages are presented with
the generic title [JavaScript Application] which sometimes makes it
difficult to know which site created them. A malicious page could
attempt to cause a prompt to appear in front of a trusted site in an
attempt to extract information such as passwords from the user. In
the fixed version these prompts will contain the hostname from the
page which created it (MFSA 2005-54; CVE-2005-2268).

Parts of the browser UI relied too much on DOM node names without
taking different namespaces into account and verifying that nodes
really were of the expected type. An XHTML document could be used to
create fake elements, for example, with content-defined properties
that the browser would access as if they were the trusted built-in
properties of the expected HTML elements. The severity of the
vulnerability would depend on what the attacker could convince the
victim to do, but could result in executing user-supplied script with
elevated 'chrome' privileges. This could be used to install malicious
software on the victim's machine (MFSA 2005-55; CVE-2005-2269).

Improper cloning of base objects allowed web content scripts to walk
up the prototype chain to get to a privileged object. This could be
used to execute code with enhanced privileges (MFSA 2005-56;

The updated packages have been patched to address these issue.


New packages are available that fix some regression errors that
appeared in the Firefox 1.0.5 release that the patches were based on.

See also :

Solution :

Update the affected package(s).

Risk factor :

High / CVSS Base Score : 7.5
Public Exploit Available : true

Family: Mandriva Local Security Checks

Nessus Plugin ID: 20420 (mandrake_MDKSA-2005-120.nasl)

Bugtraq ID:

CVE ID: CVE-2005-1937

Ready to Amp Up Your Nessus Experience?

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

Buy Nessus Professional Now