Code execution via unchecked L2CAP fragment length
Published Dec 7, 2021 · Updated Aug 4, 2024
Buffer overflow in the BLE stack in Contiki-NG 4.4 and earlier allows physically proximate attackers to execute code via crafted L2CAP frames. The input_l2cap_frame_flow_channel function passes attacker-controlled fragment lengths to memcpy without ensuring that the destination receive buffer has enough remaining space. Reachability requires BLE L2CAP credit-based flow control, and an oversized first or subsequent fragment can corrupt device memory and execute code.
Summary
What happened
Buffer overflow in the BLE stack in Contiki-NG 4.4 and earlier allows physically proximate attackers to execute code via crafted L2CAP frames. The input_l2cap_frame_flow_channel function passes attacker-controlled fragment lengths to memcpy without ensuring that the destination receive buffer has enough remaining space. Reachability requires BLE L2CAP credit-based flow control, and an oversized first or subsequent fragment can corrupt device memory and execute code.
The record
- CVE
- CVE-2020-12140
- Published
- Dec 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1190
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 7, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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