{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-8237 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-8237 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-8237 is a high-severity code injection vulnerability in Lenovo Updates, published on 10 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-8237 and fix it if it is affected.\n\nWhat it is: CVE-2016-8237 is a high-severity code injection vulnerability in Lenovo Updates, published on 10 Apr 2017. 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-2016-8237 in the wild and no public exploit code.\n\nAffected product: Lenovo Updates. 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-2016-8237/ (Markdown: https://insights.sbomify.com/CVE-2016-8237/index.md)","id":"CVE-2016-8237","markdown":"https://insights.sbomify.com/CVE-2016-8237/index.md","name":"CVE-2016-8237","record":{"aliases":["GHSA-wr24-m42c-7rjv"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Lenovo Updates","requires_auth":"none","summary":"Man-in-the-middle attackers can execute arbitrary code on systems running Lenovo Updates due to insufficient validation.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"lenovo","cpe":[{"product":"updates","vendor":"lenovo"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"Remote code execution in Lenovo Updates (not Lenovo System Update) allows man-in-the-middle attackers to execute arbitrary code.","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":"Code injection in Lenovo Updates","id":"CVE-2016-8237","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2016-8238"},"packages":[],"prev":{"headline":"Denial of service in ThinkServer RD350, RD450, RD550, RD650, TD350","id":"CVE-2016-8236"},"products":["Lenovo Updates"],"published":"2017-04-10","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-06","vendors":["Lenovo Group Ltd."]},"summary":"Man-in-the-middle attackers can execute arbitrary code on systems running Lenovo Updates due to insufficient validation.","url":"https://insights.sbomify.com/CVE-2016-8237/"}