Google Chrome before 4.0.249.89 attempts to make direct connections to web sites when all configured proxy servers are unavailable, which allows remote HTTP servers to obtain potentially sensitive information about the identity of a client user via standard HTTP logging, as demonstrated by a proxy server that was configured for the purpose of anonymity.
CPE | Name | Operator | Version |
---|---|---|---|
chrome | eq | 2.0.172.8 | |
chrome | eq | 0.3.154.3 | |
chrome | eq | 3.0.182.2 | |
chrome | eq | 0.2.149.30 | |
chrome | eq | 0.4.154.31 | |
chrome | eq | 1.0.154.39 | |
chrome | eq | 2.0.172.38 | |
chrome | eq | 1.0.154.59 | |
chrome | eq | 0.2.149.27 | |
chrome | eq | 1.0.154.53 |
secunia.com/advisories/38545
securitytracker.com/id?1023583
www.osvdb.org/62315
www.securityfocus.com/bid/38177
www.vupen.com/english/advisories/2010/0361
code.google.com/p/chromium/issues/detail?id=12303
exchange.xforce.ibmcloud.com/vulnerabilities/56212
googlechromereleases.blogspot.com/2010/02/stable-channel-update.html
oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14500
sites.google.com/a/chromium.org/dev/Home/chromium-security/chromium-security-bugs