Traffic spoofing via unauthenticated tunnel decapsulation
Published Jan 14, 2025 · Updated Nov 3, 2025
Source verification failure in IETF IPv6 version 6 allows remote attackers to route spoofed traffic through exposed tunnel endpoints. RFC 2473 tunnel exit points decapsulate IPv4-in-IPv6 or IPv6-in-IPv6 packets without validating the outer packet's source. An exposed interface that accepts protocol 4 or 41 traffic is required, enabling one-way proxying, access-control bypass, and DDoS abuse.
Summary
What happened
Source verification failure in IETF IPv6 version 6 allows remote attackers to route spoofed traffic through exposed tunnel endpoints. RFC 2473 tunnel exit points decapsulate IPv4-in-IPv6 or IPv6-in-IPv6 packets without validating the outer packet's source. An exposed interface that accepts protocol 4 or 41 traffic is required, enabling one-way proxying, access-control bypass, and DDoS abuse.
The record
- CVE
- CVE-2025-23018
- Published
- Jan 14, 2025
- Updated
- Nov 3, 2025
- Vendor
- Internet Engineering Task Force
- Product
- Internet Protocol Version 6 (IPv6)
- Classifications
- CWE-940, T1090.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- tunneltesterproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo