firefox update

Late in the day on April 24, Mozilla issued security updates for Firefox, Thunderbird and SeaMonkey. There are several security vulnerabilities patched in the latest update. Please make sure your customers are running one of the following versions: 12.0 (Firefox/Thunderbird), or 10.0.4esr (extended support release) – Firefox/Thunderbird or SeaMonkey 2.9 as soon as possible.

Mozilla products –

Firefox – versions 12 and 10.0.4 released on April 24

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

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

Thunderbird – versions 12 and 10.0.4 released on April24

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

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

SeaMonkey – version 2.8 released on April 24

http://www.seamonkey-project.org/releases/seamonkey2.9/

For those of you running firefox 3.0.14 or 3.5.3, please do a check for updates (you will need to do a runas admin for it not to be greyed out)

http://secunia.com/advisories/36711/
Mozilla Firefox Multiple Vulnerabilities

Critical: Highly critical

Impact:	Security Bypass Manipulation of data Exposure of sensitive information System access
Where:	From remote
Solution Status:	Vendor Patch

1) An array indexing error exists when allocating space for floating
point numbers. This can be exploited to trigger a memory corruption
when a specially crafted floating point number is processed.

Successful exploitation allows execution of arbitrary code.

The vulnerability is confirmed in version 3.0.14 and 3.5.3. Prior versions may also be affected.

2) An error in the form history functionality can be exploited to
disclose history entries via a specially crafted web page that triggers
the automatic filling of form fields.

3) An error when creating JavaScript web-workers recursively can be
exploited to trigger the use of freed memory and cause a crash or
potentially execute arbitrary code.

4) An error exists when parsing regular expressions used in Proxy
Auto-configuration (PAC). This can be exploited to cause a crash or
potentially execute arbitrary code via specially crafted configured PAC
files.

5) An error when processing GIF color maps can be exploited to cause a
heap-based buffer overflow and potentially execute arbitrary code via a
specially crafted GIF file.

6) An error in the “XPCVariant::VariantDataToJS()” XPCOM utility can be
exploited to execute arbitrary JavaScript code with chrome privileges.

7) An error in the implementation of the JavaScript
“document.getSelection()” function can be exploited to read text
selected on a web page in a different domain.

8) An error when downloading files can be exploited to display
different file names in the download dialog title bar and download
dialog body. This can be exploited to obfuscate file names via a
right-to-left override character and potentially trick a user into
running an executable file.

9) An error in the embedded liboggz library can be exploited to cause a crash or potentially execute arbitrary code.

10) Multiple errors in the embedded libvorbis library can be exploited to cause crashes or potentially execute arbitrary code.

11) An error in the embedded liboggplay library can be exploited to cause a crash or potentially execute arbitrary code.

12) Multiple errors in the Firefox 3 and Firefox 3.5 browser engines
can be exploited to cause crashes or potentially execute arbitrary code.

13) Multiple errors in the Firefox 3.5 browser engine can be exploited to cause crashes or potentially execute arbitrary code.

14) An error in the Firefox 3 browser engine can be exploited to cause a crash or potentially execute arbitrary code.

15) Multiple errors in the Firefox 3.5 JavaScript engine can be
exploited to cause crashes or potentially execute arbitrary code.

Security updates issued for Firefox, Thunderbird and SeaMonkey on April 24

What versions of Firefox will be supported in the future?

Patch that firefox – Vulnerabilities in 3.5.3 and 3.0.14