Memory corruption via unchecked ISO-TP single-frame length
Published Oct 6, 2023 · Updated Feb 13, 2025
Stack buffer overflow in Zephyr RTOS 3.4 and earlier allows attackers to corrupt memory through CAN ISO-TP single-frame data. The send_sf() path relies on a removable assertion before copying a caller-supplied length into the stack-allocated CAN frame. Reachability requires an application to pass attacker-controlled data across a security boundary; resulting corruption can crash the device or execute code.
Summary
What happened
Stack buffer overflow in Zephyr RTOS 3.4 and earlier allows attackers to corrupt memory through CAN ISO-TP single-frame data. The send_sf() path relies on a removable assertion before copying a caller-supplied length into the stack-allocated CAN frame. Reachability requires an application to pass attacker-controlled data across a security boundary; resulting corruption can crash the device or execute code.
The record
- CVE
- CVE-2023-3725
- Published
- Oct 6, 2023
- Updated
- Feb 13, 2025
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-120, CWE-121, CAPEC-100
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 6, 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.4
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