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

> Local attackers can gain privileges by exploiting unquoted service paths in the NVIDIA Update Service Daemon.

- **Severity:** Medium 6.8 (`AV:L/AC:L/Au:S/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:** 16 Sep 2024
- **Also known as:** GHSA-6p65-j55x-9xpq

## What is CVE-2013-0111?

CVE-2013-0111 is a medium-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

daemonu.exe (aka the NVIDIA Update Service Daemon), as distributed with the NVIDIA driver before 307.78, and Release 310 before 311.00, on Windows, lacks " (double quote) characters in the service path, which allows local users to gain privileges via a Trojan horse program.

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

It affects 1 product.


Products: Nvidia Driver.

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

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

## Is CVE-2013-0111 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-0110](https://insights.sbomify.com/CVE-2013-0110/): Privilege escalation in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0111 is a medium-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: There is no known exploitation of CVE-2013-0111 in the wild and no public exploit code.

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

## Sources

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

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