{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2018-8930 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-8930 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-8930 is a critical vulnerability in n/a, published on 22 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-8930 and fix it if it is affected.\n\nWhat it is: CVE-2018-8930 is a critical vulnerability in n/a, published on 22 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-8930 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-8930/ (Markdown: https://insights.sbomify.com/CVE-2018-8930/index.md)","id":"CVE-2018-8930","markdown":"https://insights.sbomify.com/CVE-2018-8930/index.md","name":"CVE-2018-8930","record":{"aliases":["GHSA-v58q-66pp-gf6r"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"AMD processor firmware","requires_auth":"none","summary":"Insufficient enforcement of Hardware Validated Boot in AMD processors allows attackers to bypass secure boot mechanisms.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"epyc_server_firmware","vendor":"amd"},{"product":"ryzen_firmware","vendor":"amd"},{"product":"ryzen_mobile_firmware","vendor":"amd"},{"product":"ryzen_pro_firmware","vendor":"amd"}],"cvss":{"score":9,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"The AMD EPYC Server, Ryzen, Ryzen Pro, and Ryzen Mobile processor chips have insufficient enforcement of Hardware Validated Boot, aka MASTERKEY-1, MASTERKEY-2, and MASTERKEY-3.","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-2018-8930","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":5,"next":{"headline":"Missing authorization in n/a","id":"CVE-2018-8931"},"packages":[],"prev":{"headline":"Security feature bypass in SSL VPN Client","id":"CVE-2018-8929"},"products":["n/a"],"published":"2018-03-22","related":[{"cvss_score":9,"headline":"Missing authorization in n/a","id":"CVE-2018-8933","kev_date_added":null,"published":"2018-03-22"},{"cvss_score":9,"headline":"Privilege escalation in n/a","id":"CVE-2018-8936","kev_date_added":null,"published":"2018-03-22"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Insufficient enforcement of Hardware Validated Boot in AMD processors allows attackers to bypass secure boot mechanisms.","url":"https://insights.sbomify.com/CVE-2018-8930/"}