Device crash via null buffer dereference
Published Feb 23, 2024 · Updated Aug 16, 2024
NULL pointer dereference in Silicon Laboratories Zigbee EmberZNet SDK before 7.4.0 allows remote attackers to crash devices. During high Zigbee traffic, the stack dereferences a null packet-buffer value without validating it before use. Network access is sufficient and no authentication or user interaction is required; the bounded consequence is a device crash.
Summary
What happened
NULL pointer dereference in Silicon Laboratories Zigbee EmberZNet SDK before 7.4.0 allows remote attackers to crash devices. During high Zigbee traffic, the stack dereferences a null packet-buffer value without validating it before use. Network access is sufficient and no authentication or user interaction is required; the bounded consequence is a device crash.
The record
- CVE
- CVE-2023-51394
- Published
- Feb 23, 2024
- Updated
- Aug 16, 2024
- Vendor
- Silicon Laboratories
- Product
- Zigbee EmberZNet SDK
- Classifications
- CWE-476, CAPEC-595, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 23, 2024CVE publishedPublication date reported by the CVE source.
- Aug 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=0 <7.4.0
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