# CVE-2011-0513: Privilege escalation in n/a

> Local attackers can execute arbitrary code with elevated privileges via a crafted IOCTL argument in the DriveCrypt driver.

- **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:** 20 Jan 2011
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-3mwc-76p7-h288

## What is CVE-2011-0513?

CVE-2011-0513 is a high-severity vulnerability in n/a, published on 20 Jan 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

DCR.sys driver in SecurStar DriveCrypt 5.4, 5.3, and earlier allows local users to execute arbitrary code via a crafted argument to the 0x00073800 IOCTL.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2011-0513?

It affects 1 product.


Products: Securstar Drivecrypt.

## How do I fix CVE-2011-0513?

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

## Is CVE-2011-0513 being exploited?

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

Public exploit code:

- DriveCrypt 5.3 - Local Kernel Ring0 SYSTEM (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-0513 and fix it if it is affected.

What it is: CVE-2011-0513 is a high-severity vulnerability in n/a, published on 20 Jan 2011. 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-2011-0513 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-2011-0513/ (Markdown: https://insights.sbomify.com/CVE-2011-0513/index.md)
```

## Sources

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

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