CVE-2010-0644 json
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…
published 16y ago modified 4mo ago also EUVD-2010-0675
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- google chrome 4.0.249.89
Is CVE-2010-0644 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.87% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
-
vupen.com
/english/advisories/2010/0361
vdb-entry, patch, vendor-advisory
-
googlechromereleases.blogspot.com
/2010/02/stable-channel-update.html
patch
-
sites.google.com
/a/chromium.org/dev/Home/chromium-security/chromium-security-bugs
vendor-advisory
-
secunia.com
/advisories/38545
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/38177
vdb-entry
- code.google.com /p/chromium/issues/detail?id=29914
-
securitytracker.com
/id?1023583
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A13926
vdb-entry, signature
Sources
- CVE List CVE-2010-0644
- NVD CVE-2010-0644
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Consolidate version ranges.