Code execution via unchecked DFU upload length
Published May 11, 2020 · Updated Sep 17, 2024
Buffer overflow in Zephyr RTOS USB DFU 1.14.1 and 2.1.0 allows physically proximate attackers to execute code via a crafted upload request. The DFU_UPLOAD handler uses the host-controlled wLength value to fill a fixed request buffer without capping it at USB_REQUEST_BUFFER_SIZE. A malicious host needs direct USB access to a device built with USB DFU upload support; successful memory corruption executes code on the device.
Summary
What happened
Buffer overflow in Zephyr RTOS USB DFU 1.14.1 and 2.1.0 allows physically proximate attackers to execute code via a crafted upload request. The DFU_UPLOAD handler uses the host-controlled wLength value to fill a fixed request buffer without capping it at USB_REQUEST_BUFFER_SIZE. A malicious host needs direct USB access to a device built with USB DFU upload support; successful memory corruption executes code on the device.
The record
- CVE
- CVE-2020-10019
- Published
- May 11, 2020
- Updated
- Sep 17, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-120
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 11, 2020CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=1.14.1 <unspecified
- Affected versionversion=2.1.0 <unspecified
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