Multiple vulnerabilities have been reported in Google Chrome, where some have an unknown impact while others can be exploited by malicious people bypass certain security restrictions, disclose system information, and compromise a user's system.
1) An error when handling sandboxed frames can be exploited to navigate to or close the top location.
2) An unspecified error can lead to cross-origin message leaks.
3) An error related to counter nodes can be exploited to corrupt memory.
4) An error when handling box layout may lead to a stale node.
5) An error in certain workers can lead to cross-origin message leaks.
6) A use-after-free error exists within the DOM URL handling.
7) An error when handling unicode ranges can be exploited to cause an out-of-bounds read.
This vulnerability affects builds for Linux only.
8) An error in v8 can be exploited to bypass the same origin policy.
9) An unspecified error allows bypassing the pop-up blocker.
10) A use-after-free error exists within the document script lifetime handling.
11) An error within the OGG container can be exploited to cause an out-of-bounds write.
12) An error when handling table painting may lead to a stale pointer.
13) An error within the video code may result in use of corrupt out-of-bounds structures.
14) An unspecified error exists in the handling of the DataView object.
15) An error related to a bad cast exists within the handling of text rendering.
16) An error in the WebKit context code can lead to a stale pointer.
17) An error in XSLT may leak heap addresses.
18) An error in the handling of SVG cursors can lead to a stale pointer.
19) An error when handling attributes can be exploited to corrupt the DOM tree.
20) An error when handling re-entrancy of RegExp code can lead to memory corruption.
21) An error in v8 can be exploited to access invalid memory.
The vulnerabilities are reported in versions prior to 10.0.648.127.
Solution: Upgrade to version 10.0.648.127.
Provided and/or discovered by: The vendor credits:
1) sirdarckcat, Google Security Team.
2, 5, 8) Daniel Divricean.
3, 4, 12) Martin Barbella.
6, 14, 16, 18, 19) Sergey Glazunov.
7, 10, 15) miaubiz.
9) Chamal de Silva.
11) SkyLined, Google Chrome Security Team (SkyLined) and David Weston, MSVR.
13) Tavis Ormandy, Google Security Team.
17) Chris Evans, Google Chrome Security Team.
20, 21) Christian Holler.
Original Advisory: http://googlechromereleases.blogspot.com/2011/03/chrome-stable-release.html
Do you have additional information related to this advisory?
Please provide information about patches, mitigating factors, new versions, exploits, faulty patches, links, and other relevant data by posting comments to this Advisory. You can also send this
information to email@example.com
Score: -5 Posts: 3 User Since: 23rd Nov 2010 System Score: N/A Location: N/A Last edited on 10th Mar, 2011 01:35
the new version, once installed, even from scratch, gives still a alert in PSI saying
"The version detected of Google Chrome 10.x was 10.0.648.127 while the latest version including one or more security fixes is 10.0.648.127......"
which is a ridiculous situation, the least i can say.
any comment about this absurd alert?
Score: -5 Posts: 1 User Since: 10th Mar 2011 System Score: N/A Location: KW
The same message: ""The version detected of Google Chrome 10.x was 10.0.648.127 while the latest version including one or more security fixes is 10.0.648.127" after scanning on my PC. Well, let's wait until it will be sorted out.
Score: 2347 Posts: 3,242 User Since: 19th Dec 2007 System Score: N/A Location: N/A
For the three posters above ,
You may not be aware that the comments section under any Secunia Advisory is for technical discussion of the SA itself and the vulnerabilities ; your posting creates a thread in the "vulnerabilities" sub-Forum , but it is still limited to technical input regarding the specific SA .
Your problems are with the PSI itself and not relevant to the SA itself ; besides your problem is already dealt with in other threads in other parts of the Forum (some already created/commented on by you) .