No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Thu, 11 Jun 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:espressif:esp-idf:5.5.4:*:*:*:*:*:*:* cpe:2.3:a:espressif:esp-idf:6.0:*:*:*:*:*:*:* |
Wed, 10 Jun 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 10 Jun 2026 03:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Espressif
Espressif esp-idf |
|
| Vendors & Products |
Espressif
Espressif esp-idf |
Wed, 10 Jun 2026 01:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | ESF-IDF: Out-of-Bounds Read in ESP-TEE Secure Service Wrappers | |
| Weaknesses | CWE-125 CWE-20 CWE-200 |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-06-10T16:32:10.055Z
Reserved: 2026-05-11T20:50:30.540Z
Link: CVE-2026-45329
Updated: 2026-06-10T16:16:21.028Z
Status : Analyzed
Published: 2026-06-10T02:16:32.817
Modified: 2026-06-11T18:04:26.353
Link: CVE-2026-45329
No data.
OpenCVE Enrichment
Updated: 2026-06-10T03:30:16Z