# CVE-2012-5619: Other in n/a

> Attackers can hide files in FAT file systems by exploiting improper dotfile handling, hindering forensic analysis.

- **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:** Yes
- **Published:** 29 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-5619, GHSA-4wj6-2665-qg48, UBUNTU-CVE-2012-5619

## What is CVE-2012-5619?

CVE-2012-5619 is a low-severity vulnerability in n/a, published on 29 Sep 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Sleuth Kit (TSK) 4.0.1 does not properly handle "." (dotfile) file system entries in FAT file systems and other file systems for which . is not a reserved name, which allows local users to hide activities it more difficult to conduct forensics activities, as demonstrated by Flame.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2012-5619?

It affects 1 product.


Products: Sleuthkit the Sleuth Kit.

## How do I fix CVE-2012-5619?

Upgrade to a fixed version.

## Is CVE-2012-5619 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-14531](https://insights.sbomify.com/CVE-2019-14531/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-10233](https://insights.sbomify.com/CVE-2020-10233/): Memory corruption in n/a (critical 9.1)
- [CVE-2026-40024](https://insights.sbomify.com/CVE-2026-40024/): Sleuth Kit tsk_recover Path Traversal (high 8.4)
- [CVE-2018-11737](https://insights.sbomify.com/CVE-2018-11737/): Information disclosure in n/a (high 8.1)
- [CVE-2018-11738](https://insights.sbomify.com/CVE-2018-11738/): Information disclosure in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5619 and fix it if it is affected.

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

## Sources

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

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