Package Instance

Security researchers Nicolas Grégoire and Aki
Helin independently reported that when processing a malformed
embedded XSLT stylesheet, Firefox can crash due to a memory corruption.
While there is no evidence that this is directly exploitable, there is
a possibility of remote code execution.

Security researcher regenrecht reported via
TippingPoint's Zero Day Initiative the possibility of memory corruption during
the decoding of Ogg Vorbis files. This can cause a crash during decoding and has
the potential for remote code execution.

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 regenrecht reported via
TippingPoint's Zero Day Initiative that removed child nodes of nsDOMAttribute
can be accessed under certain circumstances because of a premature notification
of AttributeChildRemoved. This use-after-free of the child nodes could possibly
allow for remote code execution.

For historical reasons Firefox has been generous in its interpretation of web
addresses containing square brackets around the host. If this host was not a
valid IPv6 literal address, Firefox attempted to interpret the host as a regular
domain name. Gregory Fleischer reported that requests made
using IPv6 syntax using XMLHttpRequest objects through a proxy may generate
errors depending on proxy configuration for IPv6. The resulting error messages
from the proxy may disclose sensitive data because Same-Origin Policy (SOP) will
allow the XMLHttpRequest object to read these error messages, allowing user
privacy to be eroded. Firefox now enforces RFC 3986 IPv6 literal syntax and that
may break links written using the non-standard Firefox-only forms that were
previously accepted.
This was fixed previously for Firefox 7.0, Thunderbird 7.0, and
SeaMonkey 2.4 but only fixed in Firefox 3.6.26 and Thunderbird 3.1.18 during
2012.