Google Chrome before 6.0.472.53 and webkitgtk before 1.2.6 do not properly handle counter nodes, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors.
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
Link | Tags |
---|---|
http://www.mandriva.com/security/advisories?name=MDVSA-2011:039 | third party advisory vendor advisory |
http://code.google.com/p/chromium/issues/detail?id=51653 | patch vendor advisory |
http://www.vupen.com/english/advisories/2011/0216 | vdb entry third party advisory |
http://secunia.com/advisories/43086 | third party advisory |
http://www.redhat.com/support/errata/RHSA-2011-0177.html | third party advisory vendor advisory |
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11736 | vdb entry third party advisory signature |
http://www.vupen.com/english/advisories/2011/0552 | vdb entry third party advisory |
http://googlechromereleases.blogspot.com/2010/09/stable-and-beta-channel-updates.html | vendor advisory |