Package Instance

Firefox prevents the dropping of javascript: links onto a frame
to prevent malicious sites from tricking users into performing a cross-site
scripting (XSS) attacks on themselves. Security researcher Soroush
Dalili reported a way to bypass this protection.

Security researcher Mariusz Mlynski reported that an
attacker able to convince a potential victim to set a new home page by dragging
a link to the "home" button can set that user's home page to a
javascript: URL. Once this is done the attacker's page can cause
repeated crashes of the browser, eventually getting the script URL loaded in the
privileged about:sessionrestore context.

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.In general these flaws cannot be exploited through email in the Thunderbird
and SeaMonkey products because scripting is disabled, but are potentially a risk
in browser or browser-like contexts in those products.

Security researcher Atte Kettunen from OUSPG found two
issues with Firefox's handling of SVG using the Address Sanitizer tool. The
first issue, critically rated, is a use-after-free in SVG animation that could
potentially lead to arbitrary code execution. The second issue is rated moderate
and is an out of bounds read in SVG Filters. This could potentially incorporate
data from the user's memory, making it accessible to the page content.

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.In general these flaws cannot be exploited through email in the Thunderbird
and SeaMonkey products because scripting is disabled, but are potentially a risk
in browser or browser-like contexts in those products.

Mozilla community member Daniel Glazman of Disruptive
Innovations reported a crash when accessing a keyframe's cssText after dynamic
modification. This crash may be potentially exploitable.
Firefox 3.6 and Thunderbird 3.1 are not affected by this
vulnerability.

Security researcher Atte Kettunen from OUSPG found two
issues with Firefox's handling of SVG using the Address Sanitizer tool. The
first issue, critically rated, is a use-after-free in SVG animation that could
potentially lead to arbitrary code execution. The second issue is rated moderate
and is an out of bounds read in SVG Filters. This could potentially incorporate
data from the user's memory, making it accessible to the page content.

Mozilla developer Matt Brubeck reported that
window.fullScreen is writeable by untrusted content now that the DOM fullscreen
API is enabled. Because window.fullScreen does not include
mozRequestFullscreen's security protections, it could be used for UI spoofing.
This code change makes window.fullScreen read only by untrusted content, forcing
the use of the DOM fullscreen API in normal usage.
Firefox 3.6 and Thunderbird 3.1 are not affected by this
vulnerability.

Security Researcher Mike Brooks of Sitewatch reported that
if multiple Content Security Policy (CSP) headers are present on a page, they
have an additive effect page policy. Using carriage return line feed (CRLF)
injection, a new CSP rule can be introduced which allows for cross-site
scripting (XSS) on sites with a separate header injection vulnerability.
Firefox 3.6 and Thunderbird 3.1 are not affected by this
vulnerability.

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.In general these flaws cannot be exploited through email in the Thunderbird
and SeaMonkey products because scripting is disabled, but are potentially a risk
in browser or browser-like contexts in those products.