The Mozilla suite of browsers received security updates. Following updates are included in this update: Mozilla Firefox was updated on SUSE Linux Enterprise 10 and 11 to the 3.6.17 security release. Mozilla Firefox was updated on openSUSE 11.4 to the 4.0.1 security release. Mozilla Thunderbird was updated on openSUSE to the 3.1.10 security release. Mozilla Seamonkey was updated on openSUSE to the 2.0.14 security release. Mozilla XULRunner 1.9.1 was updated to 1.9.1.19. Mozilla XULRunner 1.9.2 was updated to 1.9.2.17. Following security issues were fixed: 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. Mozilla developers Boris Zbarsky, Gary Kwong, Jesse Ruderman, Michael Wu, Nils, Scoobidiver, and Ted Mielczarek reported memory safety issues which affected Firefox 4. CVE-2011-0079 Mozilla developer Scoobidiver reported a memory safety issue which affected Firefox 4 and Firefox 3.6 CVE-2011-0081 The web development team of Alcidion reported a crash that affected Firefox 4, Firefox 3.6 and Firefox 3.5. CVE-2011-0069 Ian Beer reported a crash that affected Firefox 4, Firefox 3.6 and Firefox 3.5. CVE-2011-0070 Mozilla developers Bob Clary, Henri Sivonen, Marco Bonardo, Mats Palmgren and Jesse Ruderman reported memory safety issues which affected Firefox 3.6 and Firefox 3.5. CVE-2011-0080 Aki Helin reported memory safety issues which affected Firefox 3.6 and Firefox 3.5. CVE-2011-0075 Ian Beer reported memory safety issues which affected Firefox 3.6 and Firefox 3.5. CVE-2011-0078 Martin Barbella reported a memory safety issue which affected Firefox 3.6 and Firefox 3.5. CVE-2011-0072 CVE-2011-0073: Security researcher regenrecht reported several dangling pointer vulnerabilities via TippingPoint"s Zero Day Initiative. Firefox 4 was not affected by these issues. 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. Firefox 4 was not affected by this issue. CVE-2011-0076: David Remahl of Apple Product Security reported that the Java Embedding Plugin 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. 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. Firefox 4 was not affected by this issue. CVE-2011-0068: Two crashes that could potentially be exploited to run malicious code were found in the WebGL feature and fixed in Firefox 4.0.1. In addition the WebGLES libraries could potentially be used to bypass a security feature of recent Windows versions. The WebGL feature was introduced in Firefox 4; older versions are not affected by these issues. Nils reported that the WebGLES libraries in the Windows version of Firefox were compiled without ASLR protection. An attacker who found an exploitable memory corruption flaw could then use these libraries to bypass ASLR on Windows Vista and Windows 7, making the flaw as exploitable on those platforms as it would be on Windows XP or other platforms. Mozilla researcher Christoph Diehl reported a potentially exploitable buffer overflow in the WebGLES library Yuri Ko reported a potentially exploitable overwrite in the WebGLES library to the Chrome Security Team. We thank them for coordinating with us on this fix. 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.