IPv6 packet injection via Key ID Mode 2
Published Jul 25, 2023 · Updated Aug 2, 2024
Authentication bypass in Google OpenThread border routers allows physically proximate attackers to inject arbitrary IPv6 datagrams. OpenThread treats every IEEE 802.15.4 frame marked Security Enabled as secure, even when Key ID Mode 2 uses a static key that must be handled as unsecure. Radio proximity is required; successful injection bypasses the Thread Network Key and exposes LAN devices that rely on the border router's filtering.
Summary
What happened
Authentication bypass in Google OpenThread border routers allows physically proximate attackers to inject arbitrary IPv6 datagrams. OpenThread treats every IEEE 802.15.4 frame marked Security Enabled as secure, even when Key ID Mode 2 uses a static key that must be handled as unsecure. Radio proximity is required; successful injection bypasses the Thread Network Key and exposes LAN devices that rely on the border router's filtering.
The record
- CVE
- CVE-2023-2626
- Published
- Jul 25, 2023
- Updated
- Aug 2, 2024
- Vendor
- Product
- Nest Hub
- Classifications
- CWE-287, CAPEC-115, T1659
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 25, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=10.20221207.2.100038 <10.20221207.2.100042
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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