Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 7.8 CISA Known Exploited Vulnerability

CVE-2013-5065

Microsoft Windows Kernel Privilege Escalation Vulnerability

Microsoft Windows

NDProxy.sys in the kernel in Microsoft Windows XP SP2 and SP3 and Server 2003 SP2 allows local users to gain privileges via a crafted application, as exploited in the wild in November 2013.

CVSS
7.8
HIGH
EPSS
34.7%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
28 Nov 2013
NVD

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 3 March 2022. US federal agencies were required to remediate it by 24 March 2022.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 34.7%, which is higher than 98.4% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2013-5065 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2013-5065.

What does CVE-2013-5065 affect?

CVE-2013-5065 affects Microsoft Windows. NDProxy.sys in the kernel in Microsoft Windows XP SP2 and SP3 and Server 2003 SP2 allows local users to gain privileges via a crafted application, as exploited in the wild in November 2013.

How severe is CVE-2013-5065?

CVE-2013-5065 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 34.7%, higher than 98.4% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 24 March 2022.

How should organisations respond to CVE-2013-5065?

Apply the vendor patch for Microsoft Windows as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.