# CVE-2024-8159: Deep Freeze 9.00.020.5760 - Out-of-bounds read

> An attacker can trigger an out-of-bounds read in the FarDisk.sys driver via a specific IOCTL, potentially disclosing sensitive memory contents.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:L`)
- **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:** 3 Oct 2024
- **Updated:** 3 Oct 2024
- **Also known as:** GHSA-8hwq-h6q5-348p

## What is CVE-2024-8159?

CVE-2024-8159 is a medium-severity vulnerability in Faronics DeepFreeze, published on 3 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Deep Freeze 9.00.020.5760 is vulnerable to an out-of-bounds read vulnerability by triggering the 0x70014 IOCTL code of the FarDisk.sys driver.

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

## Which versions are affected by CVE-2024-8159?


## How do I fix CVE-2024-8159?

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

## Is CVE-2024-8159 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8159 and fix it if it is affected.

What it is: CVE-2024-8159 is a medium-severity vulnerability in Faronics DeepFreeze, published on 3 Oct 2024. 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-2024-8159 in the wild and no public exploit code.

Affected product: Faronics DeepFreeze. 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-2024-8159/ (Markdown: https://insights.sbomify.com/CVE-2024-8159/index.md)
```

## Sources

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

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