{"answers":{"affected":"It affects 22 products.","exploited":"There is no known exploitation of CVE-2023-35818 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-35818 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-35818 is a medium-severity vulnerability in n/a, published on 17 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-35818 and fix it if it is affected.\n\nWhat it is: CVE-2023-35818 is a medium-severity vulnerability in n/a, published on 17 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-35818 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-35818/ (Markdown: https://insights.sbomify.com/CVE-2023-35818/index.md)","id":"CVE-2023-35818","markdown":"https://insights.sbomify.com/CVE-2023-35818/index.md","name":"CVE-2023-35818","record":{"aliases":["GHSA-hfvv-rq2c-v7xq"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["data_read","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ESP32 microcontroller","requires_auth":"none","summary":"Attackers can use electromagnetic fault injection to bypass secure boot and flash encryption, enabling cleartext data extraction or code execution on ESP32 devices.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"esp-eye_firmware","vendor":"espressif"},{"product":"esp32-d0wd-v3_firmware","vendor":"espressif"},{"product":"esp32-d0wdr2-v3_firmware","vendor":"espressif"},{"product":"esp32-devkitc_firmware","vendor":"espressif"},{"product":"esp32-devkitm-1_firmware","vendor":"espressif"},{"product":"esp32-mini-1_firmware","vendor":"espressif"},{"product":"esp32-mini-1u_firmware","vendor":"espressif"},{"product":"esp32-pico-d4_firmware","vendor":"espressif"},{"product":"esp32-pico-kit_firmware","vendor":"espressif"},{"product":"esp32-pico-mini-02_firmware","vendor":"espressif"},{"product":"esp32-pico-mini-02u_firmware","vendor":"espressif"},{"product":"esp32-pico-v3-02_firmware","vendor":"espressif"},{"product":"esp32-pico-v3-zero-devkit_firmware","vendor":"espressif"},{"product":"esp32-pico-v3-zero_firmware","vendor":"espressif"},{"product":"esp32-pico-v3_firmware","vendor":"espressif"},{"product":"esp32-u4wdh_firmware","vendor":"espressif"},{"product":"esp32-vaquita-dspg_firmware","vendor":"espressif"},{"product":"esp32-wroom-32e_firmware","vendor":"espressif"},{"product":"esp32-wroom-32ue_firmware","vendor":"espressif"},{"product":"esp32-wroom-da_firmware","vendor":"espressif"},{"product":"esp32-wrover-e_firmware","vendor":"espressif"},{"product":"esp32-wrover-ie_firmware","vendor":"espressif"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2023-35818","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Use after free in n/a","id":"CVE-2023-35823"},"packages":[],"prev":{"headline":"Server-side request forgery in DevExpress","id":"CVE-2023-35817"},"products":["n/a"],"published":"2023-07-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-31","vendors":["n/a"]},"summary":"Attackers can use electromagnetic fault injection to bypass secure boot and flash encryption, enabling cleartext data extraction or code execution on ESP32 devices.","url":"https://insights.sbomify.com/CVE-2023-35818/"}