{"answers":{"affected":"It affects 5 products.","exploited":"There is no known exploitation of CVE-2017-5721 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-5721 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-5721 is a high-severity memory corruption vulnerability in Intel Corporation NUC Kits, published on 11 Oct 2017. 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-2017-5721 and fix it if it is affected.\n\nWhat it is: CVE-2017-5721 is a high-severity memory corruption vulnerability in Intel Corporation NUC Kits, published on 11 Oct 2017. 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-2017-5721 in the wild and no public exploit code.\n\nAffected product: Intel Corporation NUC Kits. 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-2017-5721/ (Markdown: https://insights.sbomify.com/CVE-2017-5721/index.md)","id":"CVE-2017-5721","markdown":"https://insights.sbomify.com/CVE-2017-5721/index.md","name":"CVE-2017-5721","record":{"aliases":["GHSA-hg9f-cr6x-3gxw"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Intel NUC firmware","requires_auth":"high_privilege","summary":"Local attackers can execute arbitrary code on Intel NUC devices by exploiting insufficient input validation in system firmware.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"intel","cpe":[{"product":"nuc7i3bnh_firmware","vendor":"intel"},{"product":"nuc7i3bnk_firmware","vendor":"intel"},{"product":"nuc7i5bnh_firmware","vendor":"intel"},{"product":"nuc7i5bnk_firmware","vendor":"intel"},{"product":"nuc7i7bnh_firmware","vendor":"intel"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Insufficient input validation in system firmware for Intel NUC7i3BNK, NUC7i3BNH, NUC7i5BNK, NUC7i5BNH, NUC7i7BNH versions BN0049 and below allows local attackers to execute arbitrary code via manipulation of memory.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2017-10-23","github_poc":1,"max_poc_stars":17,"metasploit":0,"nuclei":0,"refs":[{"date":"2017-10-23T11:00:18Z","kind":"github_poc","ref":"https://github.com/embedi/smm_usbrt_poc","stars":17,"title":"CVE-2017-5721 Proof-of-Concept"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Memory corruption in NUC Kits","id":"CVE-2017-5721","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in NUC Kits","id":"CVE-2017-5722"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2017-5720"},"products":["NUC Kits"],"published":"2017-10-11","related":[{"cvss_score":8.4,"headline":"Hardcoded credentials in NUC Kits","id":"CVE-2017-5700","kev_date_added":null,"published":"2017-10-11"},{"cvss_score":7.5,"headline":"Security feature bypass in NUC Kits","id":"CVE-2017-5722","kev_date_added":null,"published":"2017-10-11"},{"cvss_score":7.1,"headline":"Security feature bypass in NUC Kits","id":"CVE-2017-5701","kev_date_added":null,"published":"2017-10-11"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Intel Corporation"]},"summary":"Local attackers can execute arbitrary code on Intel NUC devices by exploiting insufficient input validation in system firmware.","url":"https://insights.sbomify.com/CVE-2017-5721/"}