{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-18558 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-18558 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-18558 is a medium-severity vulnerability in n/a, published on 13 May 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-2018-18558 and fix it if it is affected.\n\nWhat it is: CVE-2018-18558 is a medium-severity vulnerability in n/a, published on 13 May 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-2018-18558 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-2018-18558/ (Markdown: https://insights.sbomify.com/CVE-2018-18558/index.md)","id":"CVE-2018-18558","markdown":"https://insights.sbomify.com/CVE-2018-18558/index.md","name":"CVE-2018-18558","record":{"aliases":["GHSA-369v-4h43-wwr9"],"analysis":{"component_type":"hardware_firmware","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"ESP-IDF bootloader","requires_auth":"none","summary":"A physically proximate attacker can bypass secure boot and execute arbitrary code in ESP-IDF if flash encryption is disabled or another write vulnerability exists.","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.4,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"An issue was discovered in Espressif ESP-IDF 2.x and 3.x before 3.0.6 and 3.1.x before 3.1.1. Insufficient validation of input data in the 2nd stage bootloader allows a physically proximate attacker to bypass secure boot checks and execute arbitrary code, by crafting an application binary that overwrites a bootloader code segment in process_segment in components/bootloader_support/src/esp_image_format.c. The attack is effective when the flash encryption feature is not enabled, or if the attacker finds a different vulnerability that allows them to write this binary to flash memory.","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-2018-18558","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Use after free in n/a","id":"CVE-2018-18559"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2018-18557"},"products":["n/a"],"published":"2019-05-13","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":"A physically proximate attacker can bypass secure boot and execute arbitrary code in ESP-IDF if flash encryption is disabled or another write vulnerability exists.","url":"https://insights.sbomify.com/CVE-2018-18558/"}