Google Chrome before 6.0.472.59 on Mac OS X does not properly implement file dialogs, which allows attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors. NOTE: this issue exists because of an incorrect fix for CVE-2010-3112 on Mac OS X.
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://code.google.com/p/chromium/issues/detail?id=45400 | permissions required |
http://code.google.com/p/chromium/issues/detail?id=53361 | exploit patch vendor advisory |
http://googlechromereleases.blogspot.com/2010/09/stable-beta-channel-updates_14.html | vendor advisory |
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A13941 | vdb entry third party advisory signature |