{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2019-17391 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-17391 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-17391 is a medium-severity vulnerability in n/a, published on 14 Nov 2019. 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-2019-17391 and fix it if it is affected.\n\nWhat it is: CVE-2019-17391 is a medium-severity vulnerability in n/a, published on 14 Nov 2019. 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-2019-17391 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-2019-17391/ (Markdown: https://insights.sbomify.com/CVE-2019-17391/index.md)","id":"CVE-2019-17391","markdown":"https://insights.sbomify.com/CVE-2019-17391/index.md","name":"CVE-2019-17391","record":{"aliases":["GHSA-6fg6-6393-xqhq"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ESP32 mask ROM","requires_auth":"none","summary":"Physical attackers can bypass secure boot and flash encryption protections on ESP32 chips by glitching the power supply to read protected eFuse keys.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"esp32-d0wd_firmware","vendor":"espressif"},{"product":"esp32-d2wd_firmware","vendor":"espressif"},{"product":"esp32-pico-d4_firmware","vendor":"espressif"},{"product":"esp32-s0wd_firmware","vendor":"espressif"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-755","name":"Improper Handling of Exceptional Conditions"}],"description":"An issue was discovered in the Espressif ESP32 mask ROM code 2016-06-08 0 through 2. Lack of anti-glitch mitigations in the first stage bootloader of the ESP32 chip allows an attacker (with physical access to the device) to read the contents of read-protected eFuses, such as flash encryption and secure boot keys, by injecting a glitch into the power supply of the chip shortly after reset.","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-2019-17391","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2019-17392"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2019-17390"},"products":["n/a"],"published":"2019-11-14","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Physical attackers can bypass secure boot and flash encryption protections on ESP32 chips by glitching the power supply to read protected eFuse keys.","url":"https://insights.sbomify.com/CVE-2019-17391/"}