Memory corruption via unchecked DFU transfer length
Published Oct 5, 2021 · Updated Sep 16, 2024
Heap-based buffer overflow in Zephyr RTOS 2.5.0 allows physically proximate attackers to corrupt memory via a crafted USB DFU request. The dfu_class_handle_req function passes the request-controlled wLength to memcpy without limiting it to CONFIG_USB_REQUEST_BUFFER_SIZE, overrunning dfu_data_worker.buf. A target must expose the USB DFU class; a successful overwrite corrupts adjacent structures, and code-execution potential depends on build-specific memory layout.
Summary
What happened
Heap-based buffer overflow in Zephyr RTOS 2.5.0 allows physically proximate attackers to corrupt memory via a crafted USB DFU request. The dfu_class_handle_req function passes the request-controlled wLength to memcpy without limiting it to CONFIG_USB_REQUEST_BUFFER_SIZE, overrunning dfu_data_worker.buf. A target must expose the USB DFU class; a successful overwrite corrupts adjacent structures, and code-execution potential depends on build-specific memory layout.
The record
- CVE
- CVE-2021-3625
- Published
- Oct 5, 2021
- Updated
- Sep 16, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-122, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 5, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=v2.5.0 <unspecified
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.
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