Firmware memory corruption via unchecked provisioning segment count
Published Jun 25, 2022 · Updated Apr 23, 2025
Out-of-bounds write in ESP-BLE-MESH in Espressif Systems ESP-IDF allows remote attackers to corrupt firmware memory during provisioning. Transaction Start PDU handling validates TotalLength but not SegN, so an invalid segment count makes the assembled message exceed its global buffer. An unauthenticated attacker must be within Bluetooth range while the device is accepting provisioning traffic; the corruption can enable control of the system.
Summary
What happened
Out-of-bounds write in ESP-BLE-MESH in Espressif Systems ESP-IDF allows remote attackers to corrupt firmware memory during provisioning. Transaction Start PDU handling validates TotalLength but not SegN, so an invalid segment count makes the assembled message exceed its global buffer. An unauthenticated attacker must be within Bluetooth range while the device is accepting provisioning traffic; the corruption can enable control of the system.
The record
- CVE
- CVE-2022-24893
- Published
- Jun 25, 2022
- Updated
- Apr 23, 2025
- Vendor
- Espressif Systems
- Product
- ESP-IDF
- Classifications
- CWE-787, CWE-788
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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=< 4.1.4
- Affected versionversion=> 4.2.0, < 4.2.4
- Affected versionversion=> 4.3.2, < 4.3.3
- Affected versionversion=> 4.4.1, < 4.4.2
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