dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2024-8159

MEDIUM · 6.4 CVSS v3.1 Published 2024-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Deep Freeze 9.00.020.5760 contains an out-of-bounds read vulnerability in the FarDisk.sys kernel-mode driver triggered via IOCTL code 0x70014, allowing a local attacker to read sensitive kernel memory information.

MitigationApply the vendor-supplied patch/update for Deep Freeze to obtain a patched version of FarDisk.sys that properly bounds-checks memory access in the 0x70014 IOCTL handler.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate FarDisk.sys driver file
    Search for FarDisk.sys in typical installation directories: C:\Program Files\Faronics\Deep Freeze\, C:\Program Files (x86)\Faronics\Deep Freeze\, or search the entire system with 'dir /s FarDisk.sys'
    Affected if The file exists on the system, indicating Deep Freeze kernel driver is present
  2. Get FarDisk.sys file version
    Right-click FarDisk.sys > Properties > Details tab, or run 'powershell (Get-Item "C:\Program Files\Faronics\Deep Freeze\FarDisk.sys").VersionInfo.FileVersion'
    Affected if Version is 9.00.020.5760 or earlier, or shows no visible patch version indicator (unpatched)
  3. Check Deep Freeze application version
    Open Deep Freeze console or check registry under HKLM\SOFTWARE\Faronics\Deep Freeze for Install_Version value, or look in Add/Remove Programs
    Affected if Deep Freeze version is 9.00.020.5760 or earlier (v9.x builds before the patch)
  4. Verify driver is loaded
    Open Command Prompt as admin and run 'sc query FarDisk' or check Device Manager for hidden/system devices, or run 'driverquery /v | findstr FarDisk'
    Affected if FarDisk driver service exists and shows as Running or Ready, indicating the vulnerable code path is active

The system is affected if FarDisk.sys version is at or below 9.00.020.5760 (or unpatched) and the driver is loaded and operational, enabling the vulnerable 0x70014 IOCTL handler to be reached.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch/update for Deep Freeze to obtain a patched version of FarDisk.sys that properly bounds-checks memory access in the 0x70014 IOCTL handler.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
16.0 hours of engineering $2,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8159 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-8159 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data