Lenovo System Update (formerly ThinkVantage System Update) before 5.06.0034 uses predictable security tokens, which allows local users to g…

published 2015-05-12 11y ago modified 2026-06-17 4mo ago also EUVD-2015-2326

cvss: 7.2; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 4.1%; EPSS 4.1% chance of exploitation in 30 days, percentile 90%
public exploits: 2; Metasploit and Exploit-DB

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.

Is CVE-2015-2219 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

2015-04-12 First public exploit (Metasploit exploit/windows/local/lenovo_systemupdate)
2015-05-12 Published

Exploit prediction

4.15% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

Metasploit exploit/windows/local/lenovo_systemupdate Lenovo System Update Privilege Escalation metasploit exploit, excellent rank, 2015-04-12
EDB-41708 Lenovo System Update - Local Privilege Escalation (Metasploit) local, 2015-04-12

CVSS scores

assigned by	version	score	vector
NVD	2.0	7.2	AV:L/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness

CWE-264 Permissions, Privileges, and Access Controls

References

support.lenovo.com /us/en/product_security/lsu_privilege
vendor-advisory
securityfocus.com /bid/74649
vdb-entry
ioactive.com /pdfs/Lenovo_System_Update_Multiple_Privilege_Escalations.pdf
securitytracker.com /id/1032268
vdb-entry

Sources

CVE List CVE-2015-2219
NVD CVE-2015-2219

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.