# CVE-2014-4076: Privilege escalation in n/a

> Local attackers can gain elevated privileges on Windows Server 2003 by sending crafted IOCTL calls to TCP/IP drivers.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wcj9-qvpq-7gwq

## What is CVE-2014-4076?

CVE-2014-4076 is a high-severity vulnerability in Microsoft Windows Server 2003, published on 11 Nov 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Microsoft Windows Server 2003 SP2 allows local users to gain privileges via a crafted IOCTL call to (1) tcpip.sys or (2) tcpip6.sys, aka "TCP/IP Elevation of Privilege Vulnerability."

Weakness: CWE-264

## Which versions are affected by CVE-2014-4076?

It affects 1 product.


Products: Microsoft Windows Server 2003.

## How do I fix CVE-2014-4076?

No fix has been published for CVE-2014-4076 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-4076 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-4076 exists.

Public exploit code:

- MS14-070 Windows tcpip!SetAddrOptions NULL Pointer Dereference (metasploit)
- Microsoft Windows Server 2003 SP2 - Local Privilege Escalation (MS14-070) (exploitdb)
- Microsoft Windows Server 2003 SP2 - TCP/IP IOCTL Privilege Escalation (MS14-070) (exploitdb)
- Windows 2k3 tcpip.sys Privilege Escalation (github_poc): https://github.com/fungoshacks/CVE-2014-4076

## Other vulnerabilities in Microsoft Windows Server 2003

- [CVE-2011-2005](https://insights.sbomify.com/CVE-2011-2005/): Microsoft Ancillary Function Driver (afd.sys) Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2013-3863](https://insights.sbomify.com/CVE-2013-3863/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-3181](https://insights.sbomify.com/CVE-2013-3181/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-0077](https://insights.sbomify.com/CVE-2013-0077/): Code injection in n/a (critical 9.3)
- [CVE-2012-0009](https://insights.sbomify.com/CVE-2012-0009/): Path traversal in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-4076 and fix it if it is affected.

What it is: CVE-2014-4076 is a high-severity vulnerability in Microsoft Windows Server 2003, published on 11 Nov 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-4076 exists.

Affected product: Microsoft Windows Server 2003. 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-2014-4076/ (Markdown: https://insights.sbomify.com/CVE-2014-4076/index.md)
```

## Sources

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

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