Heap overflow via invalid segmented-packet offset
Published Aug 15, 2022 · Updated Aug 3, 2024
Heap overflow in Nordic nRF5 SDK for Mesh 5.0 allows physically proximate attackers to corrupt memory via segmented packets. The transport reassembly path fails to reject a segment whose SegO exceeds SegN and uses that offset while placing segment data, writing past the heap-backed reassembly allocation. Reachability requires Bluetooth Mesh packet injection by a sender able to participate in the mesh; the documented outcome stops at heap corruption.
Summary
What happened
Heap overflow in Nordic nRF5 SDK for Mesh 5.0 allows physically proximate attackers to corrupt memory via segmented packets. The transport reassembly path fails to reject a segment whose SegO exceeds SegN and uses that offset while placing segment data, writing past the heap-backed reassembly allocation. Reachability requires Bluetooth Mesh packet injection by a sender able to participate in the mesh; the documented outcome stops at heap corruption.
The record
- CVE
- CVE-2022-35624
- Published
- Aug 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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