Mozilla Seamonkey was updated to the 2.0.14 security
release.

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

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-0074 , CVE-2011-0075)

Ian Beer reported memory safety issues which affected
Firefox 3.6 and Firefox 3.5. (CVE-2011-0077 , CVE-2011-0078)

Martin Barbella reported a memory safety issue which
affected Firefox 3.6 and Firefox 3.5. (CVE-2011-0072)

MFSA 2011-13 / CVE-2011-0065 / CVE-2011-0066 /
CVE-2011-0073: Security researcher regenrecht reported
several dangling pointer vulnerabilities via TippingPoint's
Zero Day Initiative.

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.