# CVE-2013-0109: Privilege escalation in n/a

> Local attackers can exploit improper exception handling in the NVIDIA Display Driver to gain privileges or cause a denial of service via a crafted application.

- **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:** 8 Apr 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-wgh6-4r95-rhc4

## What is CVE-2013-0109?

CVE-2013-0109 is a high-severity vulnerability in n/a, published on 8 Apr 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The NVIDIA driver before 307.78, and Release 310 before 311.00, in the NVIDIA Display Driver service on Windows does not properly handle exceptions, which allows local users to gain privileges or cause a denial of service (memory overwrite) via a crafted application.

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

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

It affects 1 product.


Products: Nvidia Display Driver.

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

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

## Is CVE-2013-0109 being exploited?

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

Public exploit code:

- Nvidia (nvsvc) Display Driver Service Local Privilege Escalation (metasploit)
- Nvidia (nvsvc) Display Driver Service - Local Privilege Escalation (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-0951](https://insights.sbomify.com/CVE-2012-0951/): Memory corruption in graphics drivers (high 7.8)
- [CVE-2015-5950](https://insights.sbomify.com/CVE-2015-5950/): Privilege escalation in n/a (medium 6.9)
- [CVE-2012-0952](https://insights.sbomify.com/CVE-2012-0952/): Heap overflow in control device ioctl (medium 5.0)
- [CVE-2012-0953](https://insights.sbomify.com/CVE-2012-0953/): Kernel heap contents leak race in ioctl handler (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0109 is a high-severity vulnerability in n/a, published on 8 Apr 2013. 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-2013-0109 exists.

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

## Sources

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

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