Arbitrary memory write via invalid HCI packet
Published Nov 20, 2024 · Updated Nov 25, 2024
Buffer overflow in Arm Mbed OS 6.16.0 allows attackers to perform an arbitrary memory write via a crafted HCI packet. hciTrSerialRxIncoming neither rejects an unknown packet identifier nor initializes a safe header length, allowing header bytes to overwrite the pending body pointer and parser state. Reachability requires control of packets on the HCI link; advancing the corrupted state without allocating the body buffer writes the next 16 body bytes to the chosen address.
Summary
What happened
Buffer overflow in Arm Mbed OS 6.16.0 allows attackers to perform an arbitrary memory write via a crafted HCI packet. hciTrSerialRxIncoming neither rejects an unknown packet identifier nor initializes a safe header length, allowing header bytes to overwrite the pending body pointer and parser state. Reachability requires control of packets on the HCI link; advancing the corrupted state without allocating the body buffer writes the next 16 body bytes to the chosen address.
The record
- CVE
- CVE-2024-48981
- Published
- Nov 20, 2024
- Updated
- Nov 25, 2024
- Vendor
- Arm
- Product
- Arm Mbed OS
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 20, 2024CVE publishedPublication date reported by the CVE source.
- Nov 25, 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=6.16.0
What conditions does exploitation require?
What is affected?
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