# CVE-2013-3899: Memory corruption in n/a

> Local attackers can gain elevated privileges by exploiting a memory corruption vulnerability in the Windows kernel driver win32k.sys.

- **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 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hxf2-p9h3-245g

## What is CVE-2013-3899?

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

### Official description

win32k.sys in the kernel-mode drivers in Microsoft Windows XP SP2 and SP3 and Server 2003 SP2 does not properly validate addresses, which allows local users to gain privileges via a crafted application, aka "Win32k Memory Corruption Vulnerability."

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Microsoft Windows Server 2003, Microsoft Windows Xp.

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

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

## Is CVE-2013-3899 being exploited?

There is no known exploitation of CVE-2013-3899 in the wild and no public exploit code.

## 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-2013-3899 and fix it if it is affected.

What it is: CVE-2013-3899 is a high-severity memory corruption vulnerability in Microsoft Windows Server 2003, published on 11 Dec 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-3899 in the wild and no public exploit code.

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-2013-3899/ (Markdown: https://insights.sbomify.com/CVE-2013-3899/index.md)
```

## Sources

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

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