Arbitrary code execution via unchecked descriptor length
Published Jul 22, 2021 · Updated Aug 4, 2024
Buffer overflow in STMicroelectronics STM32Cube Middleware 1.8.0 and earlier allows physically proximate attackers to execute arbitrary code. USBH_ParseInterfaceDesc() trusts if_descriptor->bLength without comparing it with the remaining configuration-descriptor buffer, so USBH_GetNextDesc() advances past the input boundary. The published proof of concept requires a crafted USB device packet supplied to an STM32H7B3 host running the MSC_Standalone application, exposing the embedded target to arbitrary code execution.
Summary
What happened
Buffer overflow in STMicroelectronics STM32Cube Middleware 1.8.0 and earlier allows physically proximate attackers to execute arbitrary code. USBH_ParseInterfaceDesc() trusts if_descriptor->bLength without comparing it with the remaining configuration-descriptor buffer, so USBH_GetNextDesc() advances past the input boundary. The published proof of concept requires a crafted USB device packet supplied to an STM32H7B3 host running the MSC_Standalone application, exposing the embedded target to arbitrary code execution.
The record
- CVE
- CVE-2021-34260
- Published
- Jul 22, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 22, 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
- Bug9 crafted USB device packetproof of concept · demonstrated
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