Mozilla Foundation Security Advisory 2011-33
Security issues addressed in SeaMonkey 2.3
- August 16, 2011
- Fixed in
- SeaMonkey 2.3
Miscellaneous memory safety hazards (rv:4.0)
Description: Mozilla identified and fixed several memory safety bugs in the browser engine used in SeaMonkey 2.2 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.
Aral Yaman reported a WebGL crash which affected SeaMonkey 2.2.
Bert Hubert and Theo Snelleman of Fox-IT reported a crash in the Ogg reader which affected SeaMonkey 2.2.
Mozilla developers and community members Robert Kaiser, Jesse Ruderman, moz_bug_r_a4, Mardeg, Gary Kwong, Christoph Diehl, Martijn Wargers, Travis Emmitt, Bob Clary and Jonathan Watt reported memory safety issues which affected SeaMonkey 2.2.
Unsigned scripts can call script inside signed JAR
String crash using WebGL shaders
Description: Michael Jordon of Context IS reported that an overly long shader program could cause a buffer overrun and crash in a string class used to store the shader source code.
Heap overflow in ANGLE library
Description: Michael Jordon of Context IS reported a potentially exploitable heap overflow in the ANGLE library used by Mozilla's WebGL implementation.
Crash in SVGTextElement.getCharNumAtPosition()
Description: Security researcher regenrecht reported via TippingPoint's Zero Day Initiative that a SVG text manipulation routine contained a dangling pointer vulnerability.
Credential leakage using Content Security Policy reports
Description: Mike Cardwell reported that Content Security Policy violation reports failed to strip out proxy authorization credentials from the list of request headers. Daniel Veditz reported that redirecting to a website with Content Security Policy resulted in the incorrect resolution of hosts in the constructed policy.
Cross-origin data theft using canvas and Windows D2D
Description: nasalislarvatus3000 reported that when using Windows D2D hardware acceleration, image data from one domain could be inserted into a canvas and read by a different domain.