{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-8231 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-8231 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-8231 is a high-severity vulnerability in Lenovo Group Ltd. Service Bridge, published on 3 Jun 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-8231 and fix it if it is affected.\n\nWhat it is: CVE-2016-8231 is a high-severity vulnerability in Lenovo Group Ltd. Service Bridge, published on 3 Jun 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-8231 in the wild and no public exploit code.\n\nAffected product: Lenovo Group Ltd. Service Bridge. 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-8231/ (Markdown: https://insights.sbomify.com/CVE-2016-8231/index.md)","id":"CVE-2016-8231","markdown":"https://insights.sbomify.com/CVE-2016-8231/index.md","name":"CVE-2016-8231","record":{"aliases":["GHSA-9qj6-pj7r-r25q"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Lenovo Service Bridge","requires_auth":"none","summary":"Attackers can bypass signature verification in Lenovo Service Bridge to insert forged certificates, potentially enabling malicious code execution.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"lenovo","cpe":[{"product":"lenovo_service_bridge","vendor":"lenovo"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"In Lenovo Service Bridge before version 4, a bug found in the signature verification logic of the code signing certificate could be exploited by an attacker to insert a forged code signing certificate.","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 Service Bridge","id":"CVE-2016-8231","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2016"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in Lenovo IBM BladeCenter HS22, HS22V, HS23, HS23E, HX5 Earlier than 66Z","id":"CVE-2016-8232"},"packages":[],"prev":{"headline":"Information disclosure in Service Bridge","id":"CVE-2016-8230"},"products":["Service Bridge"],"published":"2017-06-03","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in Service Bridge","id":"CVE-2016-8229","kev_date_added":null,"published":"2017-06-03"},{"cvss_score":7.8,"headline":"Privilege escalation in Service Bridge","id":"CVE-2016-8228","kev_date_added":null,"published":"2017-06-03"},{"cvss_score":7.5,"headline":"Information disclosure in Service Bridge","id":"CVE-2016-8230","kev_date_added":null,"published":"2017-06-03"}],"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":"Attackers can bypass signature verification in Lenovo Service Bridge to insert forged certificates, potentially enabling malicious code execution.","url":"https://insights.sbomify.com/CVE-2016-8231/"}