MFSA 2011-12: 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. Credits

MFSA 2011-14 / CVE-2011-0067: 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.

MFSA 2011-15 / CVE-2011-0076: 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.

MFSA 2011-16 / CVE-2011-0071: 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.

MFSA 2011-18 / CVE-2011-1202: 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.

Contact

The cookie settings on this website are set to 'allow all cookies' to give you the very best website experience. If you continue without changing these settings, you consent to this - but if you want, you can opt out of all cookies by clicking below.