# CVE-2014-2884: Information disclosure in n/a

> Local attackers can bypass access restrictions to obtain sensitive information about arbitrary files via specific IOCTL calls in TrueCrypt.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 19 Mar 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-52xg-h2f5-qwqf

## What is CVE-2014-2884?

CVE-2014-2884 is a low-severity vulnerability in n/a, published on 19 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The ProcessVolumeDeviceControlIrp function in Ntdriver.c in TrueCrypt 7.1a allows local users to bypass access restrictions and obtain sensitive information about arbitrary files via a (1) TC_IOCTL_OPEN_TEST or (2) TC_IOCTL_GET_SYSTEM_DRIVE_CONFIG IOCTL call.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2014-2884?

It affects 1 product.


Products: Truecrypt Project Truecrypt.

## How do I fix CVE-2014-2884?

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

## Is CVE-2014-2884 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-2885](https://insights.sbomify.com/CVE-2014-2885/): Integer overflow in n/a (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2884 and fix it if it is affected.

What it is: CVE-2014-2884 is a low-severity vulnerability in n/a, published on 19 Mar 2018. 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-2014-2884 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-2014-2884/ (Markdown: https://insights.sbomify.com/CVE-2014-2884/index.md)
```

## Sources

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

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