Mozilla updated Firefox, Thunderbird and SeaMonkey on Wednesday, March 14 to address several security vulnerabilities. The most current releases are 11.0, 10.0.3 (ESR) for Firefox and Thunderbird and 2.8 for SeaMonkey.

Note: Version 11 corresponds to Extended Support Release version 10.0.3

Version 11.0 of Firefox was released on March 14.

• https://www.mozilla.org/security/known-vulnerabilities/firefox.html

Firefox – version 10.0.3 released on March 14

• http://www.mozilla.org/en-US/firefox/10.0.3/releasenotes/

Thunderbird – version 10.0.3 released on March 14

• http://www.mozilla.org/en-US/thunderbird/10.0.3/releasenotes/

SeaMonkey – version 2.8 released on March 14

• http://www.seamonkey-project.org/releases/seamonkey2.8/

All versions prior to the 3.6.2 were updated. Please make sure you don’t have anything older than 3.5.9 or 3.0.19

I have yet to figure out where this SSL setting is to be performed. But I am looking.
It appears that only the 3.5.9 version requires the SSL setting be changed. I think the 3.0.19 version does not have this issue.

http://secunia.com/advisories/39136/
SOLUTION:
Update to version 3.5.9. Set the
“security.ssl.require_safe_negotiation” preference to “true”.

http://secunia.com/advisories/39240/
SOLUTION:
Update to version 3.0.19.

Successful exploitation (under version 3.0.18) requires that the “Firebug” addon is
installed.

If you are using 3.0.17, you can do a check for updates.
3.5.7 users are really being directed to version 3.6 it seems.

http://www.mozilla.com/en-US/products/download.html?product=firefox-3.5.8&os=win&lang=en-US

Today is a good day to patch firefox.

http://secunia.com/advisories/37699/
Mozilla Firefox Multiple Vulnerabilities
Critical:    Highly critical
Impact:     Security Bypass
Spoofing
Manipulation of data
Exposure of sensitive information
System access    Where:     From remote
Solution Status:     Vendor Patch
Solution:Update to version 3.0.16 or 3.5.6

Some vulnerabilities have been reported in Mozilla Firefox, which can be exploited by malicious people to conduct spoofing attacks, bypass certain security restrictions, manipulate certain data, disclose sensitive information, or compromise a user’s system.

1) Multiple errors in the browser engine can be exploited to corrupt memory.

2) Multiple errors in the JavaScript engine can be exploited to corrupt memory.

3) Multiple errors in the included liboggplay library can be exploited to corrupt memory.

4) An integer overflow error in the included Theora library can be exploited to cause a heap-based buffer overflow via a specially crafted video file.

5) An error in the implementation of the NTLM authentication protocol can be exploited to reflect the user’s NTLM credentials to an arbitrary application.

6) An error when handling HTTP redirections to “https://” URLs can be exploited to incorrectly display SSL indicators for an insecure page.

7) An error when handling invalid URLs can be exploited to place an arbitrary and apparently legitimate URL in the location bar.

8) An error when opening content windows from a chrome window can be exploited to execute arbitrary JavaScript code with chrome privileges via the “window.opener” property.

NOTE: This vulnerability can only be exploited via certain add-ons opening untrusted web content.

9) An error when generating “GeckoActiveXObject()” exception messages can be exploited to determine the presence of COM objects and potentially track a user across browsing sessions.