CVE-2010-0644
Description
Google Chrome before 4.0.249.89, when a SOCKS 5 proxy server is configured, sends DNS queries directly, which allows remote DNS servers to obtain potentially sensitive information about the identity of a client user via request logging, as demonstrated by a proxy server that was configured for the purpose of anonymity.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Application impact
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| chrome | 0.3.154.0 | | |
| chrome | 2.0.172.8 | | |
| chrome | 2.0.172.27 | | |
| chrome | 2.0.172.28 | | |
| chrome | 2.0.172.30 | | |
| chrome | 2.0.172.31 | | |
| chrome | 2.0.172.33 | | |
| chrome | 2.0.172.37 | | |
| chrome | 2.0.172.38 | | |
| chrome | 3.0.182.2 | | |
| chrome | 3.0.190.2 | | |
| chrome | {"endIncluding":"4.0.249.78"} | | |
| chrome | 0.2.149.27 | | |
| chrome | 0.3.154.3 | | |
| chrome | 0.4.154.18 | | |
| chrome | 0.4.154.22 | | |
| chrome | 0.4.154.31 | | |
| chrome | 0.4.154.33 | | |
| chrome | 1.0.154.36 | | |
| chrome | 1.0.154.39 | | |
| chrome | 1.0.154.42 | | |
| chrome | 1.0.154.43 | | |
| chrome | 1.0.154.46 | | |
| chrome | 1.0.154.48 | | |
| chrome | 1.0.154.52 | | |
| chrome | 3.0.193.2 | | |
| chrome | 3.0.195.21 | | |
| chrome | 3.0.195.24 | | |
| chrome | 1.0.154.59 | | |
| chrome | 3.0.195.32 | | |
| chrome | 3.0.195.33 | | |
| chrome | 0.2.149.29 | | |
| chrome | 0.2.149.30 | | |
| chrome | 0.2.152.1 | | |
| chrome | 0.2.153.1 | | |
| chrome | 1.0.154.65 | | |
| chrome | 2.0.156.1 | | |
| chrome | 2.0.157.0 | | |
| chrome | 2.0.157.2 | | |
| chrome | 2.0.158.0 | | |
| chrome | 2.0.159.0 | | |
| chrome | 2.0.169.0 | | |
| chrome | 2.0.169.1 | | |
| chrome | 2.0.170.0 | | |
| chrome | 2.0.172 | | |
| chrome | 2.0.172.2 | | |
| chrome | 1.0.154.53 | |
References
- http://code.google.com/p/chromium/issues/detail?id=29914
- http://googlechromereleases.blogspot.com/2010/02/stable-channel-update.html
- http://secunia.com/advisories/38545
- http://securitytracker.com/id?1023583
- http://sites.google.com/a/chromium.org/dev/Home/chromium-security/chromium-security-bugs
- http://www.securityfocus.com/bid/38177
- http://www.vupen.com/english/advisories/2010/0361
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A13926
- http://code.google.com/p/chromium/issues/detail?id=29914
- http://googlechromereleases.blogspot.com/2010/02/stable-channel-update.html
- http://secunia.com/advisories/38545
- http://securitytracker.com/id?1023583
- http://sites.google.com/a/chromium.org/dev/Home/chromium-security/chromium-security-bugs
- http://www.securityfocus.com/bid/38177
- http://www.vupen.com/english/advisories/2010/0361
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A13926
CWEs
CWE-200
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.