# CVE-2007-4197: Null dereference in n/a

> A NULL pointer dereference in The Sleuth Kit allows attackers to cause a denial of service via a malformed NTFS image.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-4197, GHSA-cp92-p89j-f44w

## What is CVE-2007-4197?

CVE-2007-4197 is a medium-severity vulnerability in n/a, published on 8 Aug 2007. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

icat in Brian Carrier The Sleuth Kit (TSK) before 2.09 omits NULL pointer checks in certain code paths, which allows user-assisted remote attackers to cause a denial of service (NULL dereference and application crash) and prevent examination of certain NTFS files via a malformed NTFS image.

## Which versions are affected by CVE-2007-4197?

It affects 1 product.


Products: Brian Carrier the Slueth Kit.

## How do I fix CVE-2007-4197?

Upgrade to a fixed version.

## Is CVE-2007-4197 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4196](https://insights.sbomify.com/CVE-2007-4196/): Denial of service in n/a (medium 4.3)
- [CVE-2007-4198](https://insights.sbomify.com/CVE-2007-4198/): Memory corruption in n/a (medium 4.3)
- [CVE-2007-4199](https://insights.sbomify.com/CVE-2007-4199/): Null dereference in n/a (medium 4.3)
- [CVE-2007-4200](https://insights.sbomify.com/CVE-2007-4200/): Integer overflow in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4197 and fix it if it is affected.

What it is: CVE-2007-4197 is a medium-severity vulnerability in n/a, published on 8 Aug 2007. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-4197 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-2007-4197/ (Markdown: https://insights.sbomify.com/CVE-2007-4197/index.md)
```

## Sources

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

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