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

> Local attackers can exploit a kernel memory validation flaw in the NTVDM subsystem to escalate privileges or cause a denial of service.

- **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:** 14 Aug 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-ph25-8g8x-6g6c

## What is CVE-2013-3196?

CVE-2013-3196 is a high-severity memory corruption vulnerability in Microsoft Windows 7, published on 14 Aug 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The NT Virtual DOS Machine (NTVDM) subsystem in the kernel in Microsoft Windows XP SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2, Windows 7 SP1, and Windows 8 on 32-bit platforms does not properly validate kernel-memory addresses, which allows local users to gain privileges or cause a denial of service (memory corruption) via a crafted application, aka "Windows Kernel Memory Corruption Vulnerability," a different vulnerability than CVE-2013-3197 and CVE-2013-3198.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 6 products.


Products: Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows Server 2003, Microsoft Windows Server 2008, Microsoft Windows Vista, Microsoft Windows Xp.

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

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

## Is CVE-2013-3196 being exploited?

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

## Other vulnerabilities in Microsoft Windows 7

- [CVE-2015-1635](https://insights.sbomify.com/CVE-2015-1635/): Microsoft HTTP.sys Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-2360](https://insights.sbomify.com/CVE-2015-2360/): Microsoft Win32k Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6324](https://insights.sbomify.com/CVE-2014-6324/): Microsoft Kerberos Key Distribution Center (KDC) Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6332](https://insights.sbomify.com/CVE-2014-6332/): Microsoft Windows Object Linking & Embedding (OLE) Automation Array Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2014-4148](https://insights.sbomify.com/CVE-2014-4148/): Microsoft Windows Remote Code Execution (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-3196 is a high-severity memory corruption vulnerability in Microsoft Windows 7, published on 14 Aug 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-3196 in the wild and no public exploit code.

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

## Sources

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

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