CVE-2025-23018

IPv4-in-IPv6 and IPv6-in-IPv6 tunneling (RFC 2473) do not require the validation or verification of the source of a network packet, allowing an attacker to spoof and route arbitrary traffic via an exposed network interface. This is a similar issue to CVE-2020-10136.

Weakness

The product establishes a communication channel to handle an incoming request that has been initiated by an actor, but it does not properly verify that the request is coming from the expected origin.

Affected Software

Potential Mitigations

• Use a mechanism that can validate the identity of the source, such as a certificate, and validate the integrity of data to ensure that it cannot be modified in transit using an Adversary-in-the-Middle (AITM) attack.
• When designing functionality of actions in the URL scheme, consider whether the action should be accessible to all mobile applications, or if an allowlist of applications to interface with is appropriate.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/500.html
• https://cwe.mitre.org/data/definitions/594.html
• https://cwe.mitre.org/data/definitions/595.html
• https://cwe.mitre.org/data/definitions/596.html

References

• https://datatracker.ietf.org/doc/html/rfc2473
• https://papers.mathyvanhoef.com/usenix2025-tunnels.pdf
• https://www.top10vpn.com/research/tunneling-protocol-vulnerability/