Google Chrome before 2.0.172.37 allows attackers to leverage renderer access to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unspecified vectors that trigger excessive memory allocation.
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 |
---|---|
https://exchange.xforce.ibmcloud.com/vulnerabilities/51802 | vdb entry |
http://googlechromereleases.blogspot.com/2009/07/stable-beta-update-bug-fixes.html | vendor advisory |
http://secunia.com/advisories/35844 | third party advisory vendor advisory |
http://www.vupen.com/english/advisories/2009/1924 | vdb entry vendor advisory |
http://www.securityfocus.com/bid/35723 | vdb entry |