# CVE-2018-25022: Information disclosure in n/a

> A remote attacker can discover a target user's IP address by exploiting unrestricted onion routing in the Toxcore library.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Dec 2021
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-25022, GHSA-47vr-crpx-w72f

## What is CVE-2018-25022?

CVE-2018-25022 is a low-severity vulnerability in n/a, published on 13 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Onion module in toxcore before 0.2.2 doesn't restrict which packets can be onion-routed, which allows a remote attacker to discover a target user's IP address (when knowing only their Tox Id) by positioning themselves close to target's Tox Id in the DHT for the target to establish an onion connection with the attacker, guessing the target's DHT public key and creating a DHT node with public key close to it, and finally onion-routing a NAT Ping Request to the target, requesting it to ping the just created DHT node.

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

## Which versions are affected by CVE-2018-25022?

It affects 1 product.


Products: Toktok Toxcore.

## How do I fix CVE-2018-25022?

Upgrade to a fixed version.

## Is CVE-2018-25022 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-25021](https://insights.sbomify.com/CVE-2018-25021/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25022 and fix it if it is affected.

What it is: CVE-2018-25022 is a low-severity vulnerability in n/a, published on 13 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-25022 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-2018-25022/ (Markdown: https://insights.sbomify.com/CVE-2018-25022/index.md)
```

## Sources

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

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