Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

Local Privilege Escalation in Windows NDProxy.sys

IdentifiersCVE-2013-5065CWE-269

CVE-2013-5065 is a local privilege escalation vulnerability in NDProxy.sys, a kernel-mode component in Microsoft Windows XP SP2/SP3 and Windows Server 2003 SP2. According to the provided content, the flaw allows a local user to gain elevated privileges by running a crafted application. The issue was exploited in the wild in November 2013 and was used in the Epic Turla intrusion chain as a post-compromise elevation step on Windows XP and Windows 2003 systems.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a local attacker to elevate privileges on the affected host, likely to kernel or SYSTEM-level execution given the vulnerable component is a Windows kernel driver. In practical terms, this enables full compromise of the local machine, including disabling security controls, installing persistent malware, accessing protected data, and facilitating follow-on actions such as credential theft, rootkit deployment, and lateral movement. The provided content indicates the vulnerability was used operationally in the wild as part of the Epic Turla campaign.

Mitigation

If you can’t patch tonight, do this now.

Where patching or platform replacement is not immediately possible, reduce exposure by preventing untrusted code execution on affected hosts, restricting local logon and application execution, enforcing least privilege, and using application allowlisting. Monitor for suspicious execution of untrusted local applications and signs of privilege escalation on legacy Windows XP/2003 systems. Because exploitation requires local code execution, hardening initial access vectors such as spearphishing-delivered payloads and watering-hole malware can materially reduce risk.

Remediation

Patch, then assume compromise.

Apply the Microsoft security update that addresses CVE-2013-5065 on affected Windows XP SP2/SP3 and Windows Server 2003 SP2 systems. Because the affected platforms are legacy and out of support, the preferred remediation is migration to supported Windows versions. Any systems suspected of compromise should be investigated for post-exploitation activity, including persistence mechanisms, credential theft, and rootkit installation, because this vulnerability was exploited in the wild.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.

VALID 0 / 2 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 2003 Serveroperating_system
Microsoft CorporationWindows Xpoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence4

Every observed campaign linking this CVE to a named adversary.

Associated malware3

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.