LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25022: The Onion module in toxcore before 0.2.2 doesn't restrict which packets can be onion-routed, which allows a...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-25022 is a privacy vulnerability in toxcore before 0.2.2. A remote attacker who knows a user’s Tox ID could potentially cause traffic behavior that reveals the user’s IP address. This matters most where Tox is used for anonymity or sensitive communications.

Executive priority

Treat this as targeted privacy exposure, not a broad infrastructure emergency based on the available evidence. Prioritize remediation where Tox protects sensitive users, locations, or operational anonymity.

Technical view

The toxcore Onion module did not sufficiently restrict which packet types could be onion-routed. Sources describe NAT Ping Request handling through onion routing as the path to IP discovery. The fix appears tied to toxcore 0.2.2 and related packet filtering changes.

Likely exposure

Exposure is likely limited to applications or services using toxcore before 0.2.2. The source bundle does not identify specific downstream products or distributions, so asset owners must map their own Tox client or toxcore dependency usage.

Exploitation context

The CVE description describes a remote attack requiring knowledge of the target’s Tox ID and favorable DHT positioning. The bundle does not show KEV listing, public exploitation in the wild, or a CVSS score.

Researcher notes

Evidence supports an onion-routing packet restriction flaw fixed around toxcore 0.2.2. The provided data lacks CVSS, CWE mapping, downstream affected products, and exploitation-in-the-wild confirmation.

Mitigation direction

  • Identify any toxcore dependency or bundled Tox client version.
  • Upgrade toxcore to 0.2.2 or later where applicable.
  • Review TokTok release guidance before deploying fixes.
  • Prioritize systems where IP privacy is a security requirement.

Validation and detection

  • Inventory applications that embed or package toxcore.
  • Confirm deployed toxcore versions are not older than 0.2.2.
  • Review dependency lockfiles, build artifacts, and vendor package metadata.
  • Check whether privacy-sensitive users rely on affected Tox functionality.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-25022 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.