Arbitrary memory write via failed HCI allocation
Published Nov 20, 2024 · Updated Nov 25, 2024
Buffer overflow in Arm Mbed OS 6.16.0 allows remote attackers to write arbitrary memory via oversized HCI packets. In hciTrSerialRxIncoming, a failed packet-body allocation leaves the parser in its header state, so subsequent bytes overrun the four-byte hdrRx buffer and can replace its destination pointer and state variable. No authentication or user interaction is required; successful exploitation corrupts attacker-chosen memory but has no reported confidentiality or availability impact.
Summary
What happened
Buffer overflow in Arm Mbed OS 6.16.0 allows remote attackers to write arbitrary memory via oversized HCI packets. In hciTrSerialRxIncoming, a failed packet-body allocation leaves the parser in its header state, so subsequent bytes overrun the four-byte hdrRx buffer and can replace its destination pointer and state variable. No authentication or user interaction is required; successful exploitation corrupts attacker-chosen memory but has no reported confidentiality or availability impact.
The record
- CVE
- CVE-2024-48985
- 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?
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