Description
ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. In versions 5.5.4 and 6.0, several ESP-TEE secure-service wrappers in esp_secure_services.c and esp_secure_services_iram.c validated only some of the caller-supplied pointer arguments, leaving input pointer arguments unchecked. Because the underlying TEE-protected hardware peripherals (e.g., ECC, SHA, SPI) run in RISC-V machine mode (M-mode) with full address-space access, a caller could supply pointers into TEE-exclusive memory as inputs, causing the peripheral to read TEE memory and return results derived from it to the REE. Depending on the wrapper, the result contains raw bytes from TEE memory, a computed function of TEE memory recoverable through repeated calls, or a single bit per call that forms an oracle for incremental disclosure of TEE-resident sensitive data. This issue has been patched in versions 5.5.5 and 6.0.1.
Affected products
espressif: esp-idf
References4
- github.com/espressif/esp-idf/security/advisories/GHSA-w82j-7q63… MitigationPatchVendor Advisory
- github.com/espressif/esp-idf/commit/145ba4c42dc8283054cfde9a1c3… Patch
- github.com/espressif/esp-idf/commit/7867f4a57560bf9fc4a931e37ba… Patch
- github.com/espressif/esp-idf/commit/eebabaff2fdc273b1530fe66e55… Patch
Metrics
- CVSS 3.1
-
6.5
MEDIUM
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N - EPSS — exploit probability
- 0% percentile: 2 · as of 15 November 2026
- CWE
- CWE-20CWE-125CWE-200
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.