Package Instance

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.

Security researcher Paul Stone reported that a
Java applet could be used to mimic interaction with form autocomplete
controls and steal entries from the form history.Firefox 4 was not affected by this issue.

Security researcher regenrecht reported several
dangling pointer vulnerabilities via TippingPoint's Zero Day
Initiative.Firefox 4 was not affected by these issues.

David Remahl of Apple Product Security reported
that the Java Embedding Plugin (JEP) shipped with the Mac OS X versions
of Firefox could be exploited to obtain elevated access to resources on
a user's system.Firefox 4 was not affected by this issue.

Chris Evans of the Chrome Security Team reported
that the XSLT generate-id() function returned a string that revealed
a specific valid address of an object on the memory heap. It is possible
that in some cases this address would be valuable information that could
be used by an attacker while exploiting a different memory corruption
but, in order to make an exploit more reliable or work around mitigation
features in the browser or operating system.

Security researcher Soroush Dalili reported that
the resource: protocol could be exploited to allow directory traversal
on Windows and the potential loading of resources from non-permitted
locations. The impact would depend on whether interesting files existed
in predictable locations in a useful format. For example, the existence
or non-existence of particular images might indicate whether certain
software was installed.