{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-15894 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15894 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15894 is a medium-severity vulnerability in n/a, published on 7 Oct 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-15894 and fix it if it is affected.\n\nWhat it is: CVE-2019-15894 is a medium-severity vulnerability in n/a, published on 7 Oct 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-15894 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-15894/ (Markdown: https://insights.sbomify.com/CVE-2019-15894/index.md)","id":"CVE-2019-15894","markdown":"https://insights.sbomify.com/CVE-2019-15894/index.md","name":"CVE-2019-15894","record":{"aliases":["GHSA-hgpr-gf26-38f8"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"ESP32 firmware","requires_auth":"none","summary":"Physical fault injection bypasses Secure Boot verification, allowing unverified code execution if Flash Encryption is not permanently enabled.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"esp-idf","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":[{"id":"CWE-755","name":"Improper Handling of Exceptional Conditions"}],"description":"An issue was discovered in Espressif ESP-IDF 2.x, 3.0.x through 3.0.9, 3.1.x through 3.1.6, 3.2.x through 3.2.3, and 3.3.x through 3.3.1. An attacker who uses fault injection to physically disrupt the ESP32 CPU can bypass the Secure Boot digest verification at startup, and boot unverified code from flash. The fault injection attack does not disable the Flash Encryption feature, so if the ESP32 is configured with the recommended combination of Secure Boot and Flash Encryption, then the impact is minimized. If the ESP32 is configured without Flash Encryption then successful fault injection allows arbitrary code execution. To protect devices with Flash Encryption and Secure Boot enabled against this attack, a firmware change must be made to permanently enable Flash Encryption in the field if it is not already permanently enabled.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Security feature bypass in n/a","id":"CVE-2019-15894","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":"Missing authorization in n/a","id":"CVE-2019-15895"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2019-15893"},"products":["n/a"],"published":"2019-10-07","related":[{"cvss_score":9.3,"headline":"ESF-IDF: Out-of-Bounds Write in ESP-TEE Secure Service Wrappers","id":"CVE-2026-45328","kev_date_added":null,"published":"2026-06-10"},{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2024-53406","kev_date_added":null,"published":"2025-03-13"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2021-28139","kev_date_added":null,"published":"2021-09-07"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2024-33453","kev_date_added":null,"published":"2024-10-17"},{"cvss_score":8.1,"headline":"Weak cryptography in n/a","id":"CVE-2019-12587","kev_date_added":null,"published":"2019-09-04"},{"cvss_score":7.5,"headline":"ESF-IDF: Remote Null Pointer Dereference in WebSocket Server","id":"CVE-2026-45541","kev_date_added":null,"published":"2026-06-10"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2024-51428","kev_date_added":null,"published":"2024-11-07"}],"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 fault injection bypasses Secure Boot verification, allowing unverified code execution if Flash Encryption is not permanently enabled.","url":"https://insights.sbomify.com/CVE-2019-15894/"}