Bug 188827 - CVE-2006-1733 Accessing XBL compilation scope via valueOf.call()
Summary: CVE-2006-1733 Accessing XBL compilation scope via valueOf.call()
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 5
Hardware: All
OS: Linux
medium
urgent
Target Milestone: ---
Assignee: Christopher Aillon
QA Contact:
URL:
Whiteboard: reported=20060412,source=mozilla,emba...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-13 03:26 UTC by Josh Bressers
Modified: 2007-11-30 22:11 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-04-27 12:55:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Josh Bressers 2006-04-13 03:26:47 UTC
Accessing XBL compilation scope via valueOf.call()


moz_bug_r_a4 discovered that the compilation scope of privileged built-in
XBL bindings was not fully protected from web content and could be accessed
by calling valueOf.call() and valueOf.apply() on a method of that binding.
This could then be used to compile and run attacker-supplied JavaScript,
giving it the privileges of the binding which would allow an attacker to
install malware such as viruses and password sniffers.

shutdown  reported an alternate way to get to XBL compilation scope by
inserting an XBL method into the DOM's document.body prototype chain.

Note: Thunderbird shares the JavaScript engine with Firefox and could be
vulnerable if JavaScript were to be enabled in mail. This is not the default
setting and we strongly discourage users from running JavaScript in mail.

Workaround

Disable JavaScript until you can upgrade to a fixed version.

References

[1]https://bugzilla.mozilla.org/show_bug.cgi?id=312871
[2]https://bugzilla.mozilla.org/show_bug.cgi?id=313236
[3]https://bugzilla.mozilla.org/show_bug.cgi?id=313375


This issue also affects FC4

Comment 1 Josh Bressers 2006-04-27 12:55:59 UTC
These issues have been resolved in FEDORA-2006-411 for FC5 and FEDORA-2006-410
for FC4


Note You need to log in before you can comment on or make changes to this bug.