Memory corruption via unchecked Bluetooth buffer copies
Published Sep 26, 2023 · Updated Jun 18, 2025
Buffer overflows in Zephyr RTOS 3.4 and earlier allow attackers to corrupt memory through unchecked Bluetooth subsystem inputs. Bluetooth audio, connection, mesh, and shell routines use strcpy or memcpy to copy names, keys, confirmation values, and advertising data without destination-size enforcement. The affected paths require enabled Bluetooth features and attacker control of a copied value; successful corruption can crash the device or execute code.
Summary
What happened
Buffer overflows in Zephyr RTOS 3.4 and earlier allow attackers to corrupt memory through unchecked Bluetooth subsystem inputs. Bluetooth audio, connection, mesh, and shell routines use strcpy or memcpy to copy names, keys, confirmation values, and advertising data without destination-size enforcement. The affected paths require enabled Bluetooth features and attacker control of a copied value; successful corruption can crash the device or execute code.
The record
- CVE
- CVE-2023-4264
- Published
- Sep 26, 2023
- Updated
- Jun 18, 2025
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-122, CWE-120, CWE-121
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 26, 2023CVE publishedPublication date reported by the CVE source.
- Jun 18, 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=0 <=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