Google heeft weer een nieuwe uitgave van zijn browser Chrome naar buiten gebracht, met ditmaal 3.0.195.33 als het versienummer. In versie 3.0.x is er onder andere aan de snelheid van het programma gewerkt. Andere noemenswaardige verbeteringen zijn de nieuwe tabpagina en de uitbreiding van de html5-mogelijkheden, bijvoorbeeld de <video>-tag. De aankondigingen van de laatste twee uitgaves, waar slechts enkele dagen tussen zit, zien er als volgt uit:
Stable Update: Fix Google Chrome not Starting
Google Chrome's Stable channel has been updated to 3.0.195.33 to fix a potential issue that could cause Google Chrome to stop working and a security issue.
This release removes a dependency on a Windows library (t2embed.dll) that is not required by Google Chrome. If that library is missing or the user does not have permission to read it, earlier versions of Google Chrome would fail silently.
Security Fix:
CVE-2009-2816 Custom headers incorrectly sent for CORS OPTIONS request
A malicious web site operator could set custom HTTP headers on cross-origin OPTIONS requests.
More info: https://bugs.webkit.org/show_bug.cgi?id=28446.
Stable Channel Update
The stable channel has been updated to 3.0.195.32, and includes the following security and stability fixes:Security Fixes:
- Resolved a history issue that affected going back from queries in Google Maps. (Issue: 21353)
- Fixed issue with Adobe Acrobat Reader 9.2, where no content would be displayed. (Issue: 24883)
- Fixed an infinite loop in AAC decoding. (Webkit Issue: 27239)
- Fixed a top crasher. (Issue: 22205)
- Fix issues where setInterval sometimes eats 100% CPU. (Issue: 25892)
CVE-2009-XXXX User not warned for some file types that can execute JavaScript
The user was not warned about certain possibly dangerous file types such as SVG, MHT and XML files. In some browsers, JavaScript can execute within these types of files. Because the JavaScript runs in the local context, it may be able to access local resources.
More info: http://code.google.com/p/chromium/issues/detail?id=23979
(This issue will be made public once a majority of users are up to date with the fix.)
CVE-2009-XXXX Possible memory corruption in the Gears plugin
A malicious site could use the Gears SQL API to put SQL metadata into a bad state, which could cause a subsequent memory corruption. This may lead to a Gears plugin crash or possibly arbitrary code execution.
More info: http://code.google.com/p/chromium/issues/detail?id=26179
(This issue will be made public once a majority of users are up to date with the fix.)
:fill(white):strip_exif()/i/2002189289.jpeg?f=thumbmedium)
:strip_exif()/u/300600/mona_tux_christmas.gif?f=community){kind=small}
:strip_icc():strip_exif()/u/150799/ice.jpg?f=community){kind=small}
/u/96077/crop5b8d7c89bae9d_cropped.png?f=community){kind=small}
:strip_icc():strip_exif()/u/219438/crop5719edde060e2_cropped.jpeg?f=community){kind=small}
/u/63741/crop5dd40c0281913_cropped.png?f=community){kind=small}
:strip_icc():strip_exif()/u/280388/2748055456a9378956814s.jpg?f=community){kind=small}