{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-2219 exists.","fix":"No fix has been published for CVE-2015-2219 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-2219 is a high-severity vulnerability in n/a, published on 12 May 2015. 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-2015-2219 and fix it if it is affected.\n\nWhat it is: CVE-2015-2219 is a high-severity vulnerability in n/a, published on 12 May 2015. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-2219 exists.\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-2219/ (Markdown: https://insights.sbomify.com/CVE-2015-2219/index.md)","id":"CVE-2015-2219","markdown":"https://insights.sbomify.com/CVE-2015-2219/index.md","name":"CVE-2015-2219","record":{"aliases":["GHSA-fc78-c6mj-8vjm"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Lenovo System Update","requires_auth":"low_privilege","summary":"Local attackers can escalate privileges by exploiting predictable security tokens in the Lenovo System Update service via a named pipe.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"system_update","vendor":"lenovo"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"AV:L/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"Lenovo System Update (formerly ThinkVantage System Update) before 5.06.0034 uses predictable security tokens, which allows local users to gain privileges by sending a valid token with a command to the System Update service (SUService.exe) through an unspecified named pipe.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2015-04-12","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2015-04-12","kind":"exploitdb","ref":"41708","stars":null,"title":"Lenovo System Update - Local Privilege Escalation (Metasploit)"},{"date":"2015-04-12","kind":"metasploit","ref":"exploit/windows/local/lenovo_systemupdate","stars":null,"title":"Lenovo System Update Privilege Escalation"}],"tier":"weaponised"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2015-2219","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2015"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2015-2220"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2015-2218"},"products":["n/a"],"published":"2015-05-12","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"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2015-7336","kev_date_added":null,"published":"2020-03-27"}],"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":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Local attackers can escalate privileges by exploiting predictable security tokens in the Lenovo System Update service via a named pipe.","url":"https://insights.sbomify.com/CVE-2015-2219/"}