# CVE-2020-10233: Memory corruption in n/a

> A heap-based buffer over-read in The Sleuth Kit allows attackers to cause denial of service or disclose sensitive memory contents via crafted NTFS images.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-10233, GHSA-qv49-69cc-w47j, UBUNTU-CVE-2020-10233

## What is CVE-2020-10233?

CVE-2020-10233 is a critical memory corruption vulnerability in n/a, published on 8 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In version 4.8.0 and earlier of The Sleuth Kit (TSK), there is a heap-based buffer over-read in ntfs_dinode_lookup in fs/ntfs.c.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2020-10233?

It affects 1 product.


Products: Sleuthkit the Sleuth Kit.

## How do I fix CVE-2020-10233?

Upgrade to a fixed version.

## Is CVE-2020-10233 being exploited?

There is no known exploitation of CVE-2020-10233 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-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)
- [CVE-2018-11739](https://insights.sbomify.com/CVE-2018-11739/): Information disclosure in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10233 and fix it if it is affected.

What it is: CVE-2020-10233 is a critical memory corruption vulnerability in n/a, published on 8 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10233 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-2020-10233/ (Markdown: https://insights.sbomify.com/CVE-2020-10233/index.md)
```

## Sources

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

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