Security fixes and rewards:
Please see the Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.
Congratulations to Pinkie Pie for completing challenge: 64-bit exploit.
Full details about what changes are in this release are available in the SVN revision log. Interested in hopping on the stable channel? Find out how. If you find a new issue, please let us know by filing a bug.
Please see the Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.
- [161564] High CVE-2012-5138: Incorrect file path handling. Credit to Google Chrome Security Team (Jüri Aedla).
- [$7331] [162835] High CVE-2012-5137: Use-after-free in media source handling. Credit to Pinkie Pie.
Congratulations to Pinkie Pie for completing challenge: 64-bit exploit.
Full details about what changes are in this release are available in the SVN revision log. Interested in hopping on the stable channel? Find out how. If you find a new issue, please let us know by filing a bug.
Karen Grunberg
Google Chrome
6 comments:
Is it me or you just payed "LEET" money? :) 7331? Come on :)
7.5K USD for a full exploit? Last time I heard the reward was 60K.
Can anyone tell us when this particular issue will be fixed? Font rendering is broken since Chrome v22 at least on my config:
Win7X64SP1
https://code.google.com/p/chromium/issues/detail?id=146407&q=cleartype&colspec=ID%20Pri%20Mstone%20ReleaseBlock%20OS%20Area%20Feature%20Status%20Owner%20Summary
There's a lengthy thread there where people are complaining about it, but no answer of what's wrong & when it could be fixed...
obat stroke
My font rendering is also still broken, since Chrome 22. I am using the browser "Iron" at the moment, based on the previous Chrome 21.
Post a Comment