Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-65092: CWE-125: Out-of-bounds Read in espressif esp-idf

0
Medium
VulnerabilityCVE-2025-65092cvecve-2025-65092cwe-125cwe-191
Published: Fri Nov 21 2025 (11/21/2025, 21:33:03 UTC)
Source: CVE Database V5
Vendor/Project: espressif
Product: esp-idf

Description

ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. In versions 5.5.1, 5.4.3, and 5.3.4, when the ESP32-P4 uses its hardware JPEG decoder, the software parser lacks necessary validation checks. A specially crafted (malicious) JPEG image could exploit the parsing routine and trigger an out-of-bounds array access. This issue has been fixed in versions 5.5.2, 5.4.4, and 5.3.5. At time of publication versions 5.5.2, 5.4.4, and 5.3.5 have not been released but are fixed respectively in commits 4b8f585, c79cb4d, and 34e2726.

AI-Powered Analysis

AILast updated: 11/21/2025, 22:02:21 UTC

Technical Analysis

CVE-2025-65092 is a medium severity vulnerability identified in the Espressif Internet of Things Development Framework (esp-idf), specifically affecting versions 5.5.1, 5.4.3, and 5.3.4. The flaw exists in the JPEG decoding component of the ESP32-P4 hardware platform, where the software parser fails to perform adequate validation on JPEG image data. This lack of validation permits an attacker to craft malicious JPEG images that cause out-of-bounds reads during parsing, classified under CWE-125 (Out-of-bounds Read) and CWE-191 (Integer Underflow). Such out-of-bounds reads can lead to disclosure of sensitive memory contents or cause application crashes, potentially destabilizing the device or leaking information. The vulnerability is exploitable remotely over the network without requiring any privileges or user interaction, as the JPEG decoder processes images autonomously. However, the impact is limited to information disclosure and does not extend to code execution or system compromise. Espressif has addressed the issue in unreleased patches (versions 5.5.2, 5.4.4, and 5.3.5) with specific commits that add necessary validation checks to the JPEG parser. No public exploits have been observed, but the vulnerability poses a risk to IoT devices relying on vulnerable esp-idf versions, especially those processing JPEG images from untrusted sources.

Potential Impact

For European organizations, the primary impact of CVE-2025-65092 lies in the potential exposure of sensitive information from ESP32-P4 based IoT devices that utilize the vulnerable esp-idf versions. These devices are commonly deployed in smart home systems, industrial automation, and smart city infrastructure across Europe. An attacker could remotely send malicious JPEG images to affected devices, causing out-of-bounds reads that may leak memory contents, potentially revealing sensitive operational data or cryptographic material. While the vulnerability does not allow code execution, the resulting instability or information leakage could undermine device reliability and confidentiality, impacting critical infrastructure or consumer privacy. The risk is heightened in sectors with extensive IoT deployments such as manufacturing, energy, and public services. Additionally, the lack of required authentication or user interaction lowers the barrier for exploitation, increasing the threat surface. Organizations failing to update to patched esp-idf versions may face increased exposure to targeted attacks or reconnaissance by threat actors.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Inventory all ESP32-P4 based IoT devices and identify those running esp-idf versions 5.5.1, 5.4.3, or 5.3.4. 2) Plan and prioritize firmware updates to esp-idf versions 5.5.2, 5.4.4, or 5.3.5 once officially released, applying the patches that fix the JPEG parser validation. 3) If immediate patching is not possible, restrict network exposure of vulnerable devices by segmenting IoT networks and applying strict ingress filtering to block untrusted JPEG image inputs. 4) Monitor network traffic for anomalous JPEG image transfers or malformed image payloads targeting IoT devices. 5) Employ runtime protections or anomaly detection on IoT devices to detect crashes or abnormal behavior related to JPEG decoding. 6) Engage with device vendors to confirm patch availability and deployment timelines. 7) Incorporate this vulnerability into risk assessments and incident response plans for IoT infrastructure. These targeted steps go beyond generic patching advice by emphasizing device inventory, network segmentation, and monitoring specific to the JPEG decoding vector.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-11-17T20:55:34.691Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6920de31ac1487f7bb25178a

Added to database: 11/21/2025, 9:48:33 PM

Last enriched: 11/21/2025, 10:02:21 PM

Last updated: 11/22/2025, 3:03:00 PM

Views: 17

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats