# CVE-2015-3999: Information disclosure in n/a

> Local attackers can recover sensitive filenames from unallocated disk space due to improper file overwriting in CCleaner.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g58q-h4q2-m9q3

## What is CVE-2015-3999?

CVE-2015-3999 is a low-severity vulnerability in n/a, published on 20 May 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Piriform CCleaner 3.26.0.1988 through 5.02.5101 writes the filenames to disk when overwriting files, which allows local users to obtain sensitive information by searching unallocated disk space.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2015-3999?

It affects 1 product.


Products: Piriform Ccleaner.

## How do I fix CVE-2015-3999?

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

## Is CVE-2015-3999 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3999 and fix it if it is affected.

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

## Sources

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

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