CVE-2023-35818 Vulnerability Analysis & Exploit Details

CVE-2023-35818
Vulnerability Scoring

6.8
/10
High Risk

If left unpatched, CVE-2023-35818 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Physical
    Physical access is required to exploit this vulnerability.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2023-35818 Details

Status: Modified

Last updated: 🕗 21 Nov 2024, 08:08 UTC
Originally published on: 🕓 17 Jul 2023, 16:15 UTC

Time between publication and last update: 492 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVE-2023-35818 Vulnerability Summary

CVE-2023-35818: An issue was discovered on Espressif ESP32 3.0 (ESP32_rev300 ROM) devices. An EMFI attack on ECO3 provides the attacker with a capability to influence the PC value at the CPU context level, regardless of Secure Boot and Flash Encryption status. By using this capability, the attacker can exploit another behavior in the chip to gain unauthorized access to the ROM download mode. Access to ROM download mode may be further exploited to read the encrypted flash content in cleartext format or execute stub code.

Assessing the Risk of CVE-2023-35818

Access Complexity Graph

The exploitability of CVE-2023-35818 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2023-35818

With low attack complexity and no required privileges, CVE-2023-35818 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2023-35818, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2023-35818, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2023-35818 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2023-35818 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2023-35818 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.059% (probability of exploit)

EPSS Percentile: 27.67% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 72.33% of others.

CVE-2023-35818 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:o:espressif:esp32-d0wd-v3_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-d0wd-v3_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-d0wd-v3_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-d0wd-v3_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-d0wd-v3:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-d0wd-v3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-d0wdr2-v3_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-d0wdr2-v3_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-d0wdr2-v3_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-d0wdr2-v3_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-d0wdr2-v3:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-d0wdr2-v3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-u4wdh_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-u4wdh_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-u4wdh_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-u4wdh_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-u4wdh:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-u4wdh:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-pico-v3_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-pico-v3_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-pico-v3_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-pico-v3_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-pico-v3:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-pico-v3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-pico-v3-02_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-pico-v3-02_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-pico-v3-02_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-pico-v3-02_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-pico-v3-02:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-pico-v3-02:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-pico-d4_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-pico-d4_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-pico-d4_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-pico-d4_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-pico-d4:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-pico-d4:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-wroom-32e_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-wroom-32e_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-wroom-32e_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-wroom-32e_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-wroom-32e:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-wroom-32e:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-wroom-32ue_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-wroom-32ue_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-wroom-32ue_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-wroom-32ue_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-wroom-32ue:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-wroom-32ue:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-wroom-da_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-wroom-da_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-wroom-da_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-wroom-da_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-wroom-da:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-wroom-da:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-wrover-e_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-wrover-e_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-wrover-e_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-wrover-e_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-wrover-e:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-wrover-e:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-wrover-ie_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-wrover-ie_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-wrover-ie_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-wrover-ie_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-wrover-ie:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-wrover-ie:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-mini-1_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-mini-1_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-mini-1_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-mini-1_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-mini-1:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-mini-1:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-mini-1u_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-mini-1u_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-mini-1u_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-mini-1u_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-mini-1u:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-mini-1u:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-pico-mini-02_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-pico-mini-02_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-pico-mini-02_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-pico-mini-02_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-pico-mini-02:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-pico-mini-02:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-pico-mini-02u_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-pico-mini-02u_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-pico-mini-02u_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-pico-mini-02u_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-pico-mini-02u:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-pico-mini-02u:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-pico-v3-zero_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-pico-v3-zero_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-pico-v3-zero_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-pico-v3-zero_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-pico-v3-zero:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-pico-v3-zero:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-devkitc_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-devkitc_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-devkitc_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-devkitc_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-devkitc:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-devkitc:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-devkitm-1_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-devkitm-1_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-devkitm-1_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-devkitm-1_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-devkitm-1:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-devkitm-1:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-pico-kit_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-pico-kit_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-pico-kit_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-pico-kit_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-pico-kit:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-pico-kit:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-pico-v3-zero-devkit_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-pico-v3-zero-devkit_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-pico-v3-zero-devkit_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-pico-v3-zero-devkit_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-pico-v3-zero-devkit:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-pico-v3-zero-devkit:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp-eye_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp-eye_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp-eye_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp-eye_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp-eye:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp-eye:-:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-vaquita-dspg_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-vaquita-dspg_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:espressif:esp32-vaquita-dspg_firmware:3.1:*:*:*:*:*:*:*
    cpe:2.3:o:espressif:esp32-vaquita-dspg_firmware:3.1:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-vaquita-dspg:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-vaquita-dspg:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2023-35818: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...
  • CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
  • CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...