Just Litle Info For SRWare Iron Team.
"Tuesday, October 1, 2013
Dev Channel Update for Chrome OS
The Dev channel has been updated to 31.0.1650.6 (platform version: 4731.9.0) for all Chrome OS devices. This release contains several improvements and bug fixes.
If you find new issues, please let us know by visiting our forum or filing a bug. Interested in switching channels? Find out how. You can submit feedback using ‘Report an issue...’ in the Chrome menu (3 horizontal bars in the upper right corner of the browser).
Posted at 10:30 AM Labels: Chrome OS, Dev updates No comments
Stable Channel Update
The Chrome team is excited to announce the promotion of Chrome 30 to the Stable channel for Windows, Mac, Linux and Chrome Frame. Chrome 30.0.1599.66 contains a number of fixes and improvements, including:
Easier searching by image
A number of new apps/extension APIs
Lots of under the hood changes for stability and performance
You can read more about these changes at the Google Chrome Blog.
Security Fixes and Rewards
Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.
This update includes 50 security fixes. Below, we highlight some fixes that were either contributed by external researchers or particularly interesting. Please see the Chromium security page for more information.
[$2500] Medium CVE-2013-2906: Races in Web Audio. Credit to Atte Kettunen of OUSPG.
 Medium CVE-2013-2907: Out of bounds read in Window.prototype object. Credit to Boris Zbarsky.
[$500] Medium CVE-2013-2908: Address bar spoofing related to the “204 No Content” status code. Credit to Chamal de Silva.
[$4000] High CVE-2013-2909: Use after free in inline-block rendering. Credit to Atte Kettunen of OUSPG.
[$500] Medium CVE-2013-2910: Use-after-free in Web Audio. Credit to Byoungyoung Lee of Georgia Tech Information Security Center (GTISC).
[$1000] High CVE-2013-2911: Use-after-free in XSLT. Credit to Atte Kettunen of OUSPG.
[$1000] High CVE-2013-2912: Use-after-free in PPAPI. Credit to Chamal de Silva and 41.w4r10r(at)garage4hackers.com.
[$1000] High CVE-2013-2913: Use-after-free in XML document parsing. Credit to cloudfuzzer.
[$1000] High CVE-2013-2914: Use after free in the Windows color chooser dialog. Credit to Khalil Zhani.
 Low CVE-2013-2915: Address bar spoofing via a malformed scheme. Credit to Wander Groeneveld.
[$2000] High CVE-2013-2916: Address bar spoofing related to the “204 No Content” status code. Credit to Masato Kinugawa.
[$500] Medium CVE-2013-2917: Out of bounds read in Web Audio. Credit to Byoungyoung Lee and Tielei Wang of Georgia Tech Information Security Center (GTISC).
[$1000] High CVE-2013-2918: Use-after-free in DOM. Credit to Byoungyoung Lee of Georgia Tech Information Security Center (GTISC).
[$1000] High CVE-2013-2919: Memory corruption in V8. Credit to Adam Haile of Concrete Data.
 Medium CVE-2013-2920: Out of bounds read in URL parsing. Credit to Atte Kettunen of OUSPG.
[$1000] High CVE-2013-2921: Use-after-free in resource loader. Credit to Byoungyoung Lee and Tielei Wang of Georgia Tech Information Security Center (GTISC).
[$2000] High CVE-2013-2922: Use-after-free in template element. Credit to Jon Butler.
As usual, our ongoing internal security work responsible for a wide range of fixes:
 CVE-2013-2923: Various fixes from internal audits, fuzzing and other initiatives (Chrome 30).
 Medium CVE-2013-2924: Use-after-free in ICU. Upstream bug here.
We would also like to thank Atte Kettunen, cloudfuzzer and miaubiz for working with us during the development cycle to prevent security bugs from ever reaching the stable channel. $8000 in additional rewards were issued.
Many of the above bugs were detected using AddressSanitizer. The security issue in V8 is fixed in 18.104.22.168.
A partial list of changes is available in the SVN log. Interested in switching to a different release channel? Find out how. If you find a new issue, please let us know by filing a bug."
I think Soon soon maby 2-3 weeks you made New Version of Browser but if you wont make happy many fans quickly.