{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-7336 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-7336 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-7336 is a high-severity vulnerability in n/a, published on 27 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-7336 and fix it if it is affected.\n\nWhat it is: CVE-2015-7336 is a high-severity vulnerability in n/a, published on 27 Mar 2020. 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-2015-7336 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-2015-7336/ (Markdown: https://insights.sbomify.com/CVE-2015-7336/index.md)","id":"CVE-2015-7336","markdown":"https://insights.sbomify.com/CVE-2015-7336/index.md","name":"CVE-2015-7336","record":{"aliases":["GHSA-wpvw-pr5h-hv7q"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Lenovo System Update","requires_auth":"none","summary":"Attackers can bypass update signature checks in Lenovo System Update, potentially allowing the installation of malicious updates.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"system_update","vendor":"lenovo"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"MITRE is populating this ID because it was assigned prior to Lenovo becoming a CNA. A vulnerability was reported (fixed and publicly disclosed in 2015) in Lenovo System Update version 5.07.0008 and prior that could allow the signature check of an update to be bypassed.","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-2015-7336","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2015"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Input Validation in Jupyter Notebook","id":"CVE-2015-7337"},"packages":[],"prev":{"headline":"Race condition in n/a","id":"CVE-2015-7335"},"products":["n/a"],"published":"2020-03-27","related":[{"cvss_score":8.3,"headline":"Security feature bypass in n/a","id":"CVE-2015-2233","kev_date_added":null,"published":"2015-05-12"},{"cvss_score":7.8,"headline":"Other in Lenovo System Update","id":"CVE-2023-4632","kev_date_added":null,"published":"2023-11-08"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2015-7333","kev_date_added":null,"published":"2020-03-27"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2015-7334","kev_date_added":null,"published":"2020-03-27"},{"cvss_score":7.8,"headline":"Memory corruption in Lenovo System Update","id":"CVE-2018-9063","kev_date_added":null,"published":"2018-05-04"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2015-6971","kev_date_added":null,"published":"2017-10-02"}],"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":["n/a"]},"summary":"Attackers can bypass update signature checks in Lenovo System Update, potentially allowing the installation of malicious updates.","url":"https://insights.sbomify.com/CVE-2015-7336/"}