Local memory corruption via negative IPM size
Published Feb 18, 2024 · Updated Aug 2, 2024
Buffer overflow in the ESP32 IPM driver in Zephyr RTOS 3.5 and earlier allows local users to corrupt memory via a negative size. esp32_ipm_send compares the signed size against the shared-memory capacity, so a negative value passes the bound check and becomes a large unsigned length for memcpy. A caller able to invoke the IPM send path with a negative length can overwrite shared memory, interrupting the device and compromising data integrity.
Summary
What happened
Buffer overflow in the ESP32 IPM driver in Zephyr RTOS 3.5 and earlier allows local users to corrupt memory via a negative size. esp32_ipm_send compares the signed size against the shared-memory capacity, so a negative value passes the bound check and becomes a large unsigned length for memcpy. A caller able to invoke the IPM send path with a negative length can overwrite shared memory, interrupting the device and compromising data integrity.
The record
- CVE
- CVE-2023-6249
- Published
- Feb 18, 2024
- Updated
- Aug 2, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-704
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=* <=3.5
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