Mozilla and Google Update Their Browsers

Article by George Norman (Cybersecurity Editor)

on 20 Oct 2010

Mozilla and Google have both updated the stable version of their web browsers. Mozilla has updated its Firefox browser to version 3.6.11 while Google has updated its Chrome browser to version 7.0.517.41. Both are stability and security updates that users should get to stay safe and protected.

As Mozilla explained in the release notes, Firefox 3.6.11 fixes several stability issues and several security issues. Digging further we find out that Firefox 3.6.11 comes with 9 security advisories, out of which 5 carry the critical rating. Mozilla uses a 4-tier severity rating – critical is the most severe.

The security advisories Mozilla released for Firefox 3.6.11 are (the bold ones are critical):
MFSA 2010-72 Insecure Diffie-Hellman key exchange
MFSA 2010-71 Unsafe library loading vulnerabilities
MFSA 2010-70 SSL wildcard certificate matching IP addresses
MFSA 2010-69 Cross-site information disclosure via modal calls
MFSA 2010-68 XSS in gopher parser when parsing hrefs
MFSA 2010-67 Dangling pointer vulnerability in LookupGetterOrSetter
MFSA 2010-66 Use-after-free error in nsBarProp
MFSA 2010-65 Buffer overflow and memory corruption using document.write
MFSA 2010-64 Miscellaneous memory safety hazards (rv:1.9.2.11/ 1.9.1.14)

As Mountain View-based search engine giant Google explained, Google Chrome 7.0.517.41 brings with it an updated HTML5 parser, the File API, directory upload, full AppleScript support on Mac OS X for UI automation, and fixes for 10 security issues. Out of the 10 issues, 1 carries the critical rating, 5 carry the high rating, 2 carry the medium rating and 2 carry the low rating. Additional details on these security issues are available here.

“In this stable release, we’ve focused primarily on hundreds of bug fixes. We’ve also included a few other things that may be of interest to developers, such as full AppleScript support on Mac OS X for UI automation and implementation of the HTML5 parsing algorithm, the File API, and directory upload (via <input type="file" webkitdirectory>). Also, if you choose to block sites from setting any data in your browser’s content settings for cookies, you can now use a new dialog for managing blocked cookies in bulk,” explained Product Manager Jeff Chang.


Latest News


Sony's 'Attack of the Blockbusters Sale' Slashes Prices in Half for a Ton of PS4 Games

17 Aug 2017

How Samsung's New T5 Compares to the Old T3 Portable SSD (Infographic)

17 Aug 2017

See all