Device crash via single-frame reassembly pointer aliasing
Published Oct 12, 2021 · Updated Sep 16, 2024
NULL pointer dereference in Zephyr RTOS before 2.5.0 allows physically proximate attackers to crash devices with a malformed IEEE 802.15.4 fragment. In fragment_add_to_cache, a full-payload fragment aliases pkt with cache->pkt, so cleanup nulls the packet buffer before net_6lo_uncompress dereferences it. Reachability requires IEEE 802.15.4 radio proximity and one malformed fragment; the documented consequence is a target crash without data disclosure or modification.
Summary
What happened
NULL pointer dereference in Zephyr RTOS before 2.5.0 allows physically proximate attackers to crash devices with a malformed IEEE 802.15.4 fragment. In fragment_add_to_cache, a full-payload fragment aliases pkt with cache->pkt, so cleanup nulls the packet buffer before net_6lo_uncompress dereferences it. Reachability requires IEEE 802.15.4 radio proximity and one malformed fragment; the documented consequence is a target crash without data disclosure or modification.
The record
- CVE
- CVE-2021-3322
- Published
- Oct 12, 2021
- Updated
- Sep 16, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-476, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 12, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=>=2.4.0 <unspecified
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