# CVE-2021-46702: Information disclosure in n/a

> Local attackers can read RAM to bypass anonymity and reveal visited onion services due to improper memory freeing in Tor Browser.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5rfp-95m3-27h9

## What is CVE-2021-46702?

CVE-2021-46702 is a medium-severity vulnerability in n/a, published on 26 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Tor Browser 9.0.7 on Windows 10 build 10586 is vulnerable to information disclosure. This could allow local attackers to bypass the intended anonymity feature and obtain information regarding the onion services visited by a local user. This can be accomplished by analyzing RAM memory even several hours after the local user used the product. This occurs because the product doesn't properly free memory.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2021-46702?

It affects 1 product.


Products: Torproject Tor.

## How do I fix CVE-2021-46702?

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

## Is CVE-2021-46702 being exploited?

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

Public exploit code:

- Tor Browser 9.0.7 on Windows 10 build 10586 is vulnerable to information disclosure. This could allow local attackers to bypass the intended anonymity feature and obtain information regarding the onion services visited by a local user. This can be accomplished by analyzing RAM memory even several hours after the local user used the product. This occurs because the product doesn't properly free memory. (github_poc): https://github.com/Exmak-s/CVE-2021-46702

## Other vulnerabilities in n/a

- [CVE-2026-77638](https://insights.sbomify.com/CVE-2026-77638/): Race condition in Tor (high 8.9)
- [CVE-2026-77642](https://insights.sbomify.com/CVE-2026-77642/): Memory corruption in Tor (high 7.5)
- [CVE-2022-33903](https://insights.sbomify.com/CVE-2022-33903/): Denial of service in n/a (high 7.5)
- [CVE-2021-38385](https://insights.sbomify.com/CVE-2021-38385/): Denial of service in n/a (high 7.5)
- [CVE-2021-34548](https://insights.sbomify.com/CVE-2021-34548/): Security feature bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-46702 and fix it if it is affected.

What it is: CVE-2021-46702 is a medium-severity vulnerability in n/a, published on 26 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-46702 in the wild and no public exploit code.

Affected product: n/a. 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-2021-46702/ (Markdown: https://insights.sbomify.com/CVE-2021-46702/index.md)
```

## Sources

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

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