Memory corruption via unchecked USB buffer copies
Published Aug 12, 2023 · Updated Feb 13, 2025
Buffer overflows in Zephyr RTOS USB code before 3.4.0 allow physically proximate attackers to corrupt memory through crafted USB data. usb_dc_ep_write copies data_len bytes into a fixed 64-byte endpoint buffer, while handle_encapsulated_rsp copies buf->len bytes without checking destination capacity. Reachability requires attacker control of the copied data and length; the report does not establish whether corruption produces a crash or code execution.
Summary
What happened
Buffer overflows in Zephyr RTOS USB code before 3.4.0 allow physically proximate attackers to corrupt memory through crafted USB data. usb_dc_ep_write copies data_len bytes into a fixed 64-byte endpoint buffer, while handle_encapsulated_rsp copies buf->len bytes without checking destination capacity. Reachability requires attacker control of the copied data and length; the report does not establish whether corruption produces a crash or code execution.
The record
- CVE
- CVE-2023-4265
- Published
- Aug 12, 2023
- Updated
- Feb 13, 2025
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-120, CAPEC-100
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 12, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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=* <=3.3
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