# CVE-2010-0644: Information disclosure in n/a

> Chrome leaks client identity to remote DNS servers when using SOCKS5 proxies, exposing sensitive user information to attackers monitoring network traffic.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-prjv-5g97-fjwx

## What is CVE-2010-0644?

CVE-2010-0644 is a medium-severity vulnerability in Google Chrome, published on 18 Feb 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2010-0644?

It affects 1 product.


Products: Google Chrome.

## How do I fix CVE-2010-0644?

No fix has been published for CVE-2010-0644 yet. Limit exposure of the affected software until one is available.

## Is CVE-2010-0644 being exploited?

There is no known exploitation of CVE-2010-0644 in the wild and no public exploit code.

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0644 and fix it if it is affected.

What it is: CVE-2010-0644 is a medium-severity vulnerability in Google Chrome, published on 18 Feb 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-0644 in the wild and no public exploit code.

Affected product: Google Chrome. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2010-0644/ (Markdown: https://insights.sbomify.com/CVE-2010-0644/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2010-0644
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-0644
- OSV: https://osv.dev/vulnerability/CVE-2010-0644

---
From sbomify Insights: https://insights.sbomify.com/CVE-2010-0644/
Summaries are generated and may contain mistakes; the official description above is the record.