What is the CVSS score of CVE-2015-2219?

CVE-2015-2219 has a CVSS 2.0 base score of 7.2 (High). CVSS vector: AV:L/AC:L/Au:N/C:C/I:C/A:C. EPSS exploitation probability: 29.6%.

Is there a public PoC exploit available for CVE-2015-2219?

Yes, a public proof-of-concept exploit is available for CVE-2015-2219. Prioritise patching immediately. EPSS: 29.6%.

System Update CVE-2015-2219

HIGH

Permissions, Privileges, and Access Controls (CWE-264)

2015-05-12 cve@mitre.org

Privilege Escalation Lenovo System Update

7.2

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

7.2 HIGH

AV:L/AC:L/Au:N/C:C/I:C/A:C

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:L/AC:L/Au:N/C:C/I:C/A:C

Attack Vector

Local

Attack Complexity

Low

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

May 12, 2015 - 19:59 cve.org

HIGH 7.2

DescriptionCVE.org

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.

AnalysisAI

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. Rated high severity (CVSS 7.2), this vulnerability is low attack complexity. Public exploit code available and EPSS exploitation probability 29.6%.

Technical ContextAI

This vulnerability is classified under CWE-264. 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. Affected products include: Lenovo System Update. Version information: before 5.06.0034.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.