dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2024-29994

HIGH · 7.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 10.0.17763.5820 / 10.0.19044.4412 or later.
See remediation →
80/100
Remediation priority · High
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
Microsoft Windows SCSI Class System File Elevation of Privilege Vulnerability

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

This is a local elevation of privilege vulnerability in the Windows SCSI Class system file (driver). It allows a local authenticated attacker to gain elevated (SYSTEM) privileges by exploiting improper access controls in the SCSI class driver component.

MitigationApply the Microsoft security update for CVE-2024-29994 via Windows Update or enterprise patch management tools to address the vulnerability in the SCSI class driver.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1809Operating system
Affected:< 10.0.17763.5820
Windows 10 21h2Operating system
Affected:< 10.0.19044.4412
Windows 10 22h2Operating system
Affected:< 10.0.19045.4412
Windows 11 21h2Operating system
Affected:< 10.0.22000.2960
Windows 11 22h2Operating system
Affected:< 10.0.22621.3593
Windows 11 23h2Operating system
Affected:< 10.0.22631.3593
Windows Server 2019Operating system
Affected:< 10.0.17763.5820
Windows Server 2022Operating system
Affected:< 10.0.20348.2461

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 the SCSI class driver file
    Open Command Prompt or PowerShell and run: `dir C:\Windows\System32\drivers\scsiport.sys` or `Get-Item C:\Windows\System32\drivers\scsiport.sys`
    Affected if The file exists on the system (all listed Windows versions include this driver)
  2. Retrieve the driver file version
    Run `powershell (Get-Item 'C:\Windows\System32\drivers\scsiport.sys').VersionInfo.FileVersion` or use `verfile.vbs` or a similar version info tool
    Affected if A version number is returned - note this for comparison against the fixed versions
  3. Determine the Windows build version
    Run `winver` or `powershell [System.Environment]::OSVersion.Version` or `msinfo32` to identify the exact Windows version and build number
    Affected if The system runs any of the listed affected products (Windows 10 1809, 21h2, 22h2, Windows 11 21h2, 22h2, 23h2, Server 2019, Server 2022)
  4. Compare against fixed version ranges
    Cross-reference the scsiport.sys version and Windows build with the fixed versions: Windows 10 1809/Server 2019: 10.0.17763.5820, Windows 10 21h2: 10.0.19044.4412, Windows 10 22h2: 10.0.19045.4412, Windows 11 21h2: 10.0.22000.2960, Windows 11 22h2: 10.0.22621.3593, Windows 11 23h2: 10.0.22631.3593, Server 2022: 10.0.20348.2461
    Affected if The installed version is LOWER than the fixed version for that Windows build, or the Windows build falls within an affected version range and is not yet patched

A system is affected if it runs a Windows version listed in the affected products AND the scsiport.sys version is below the corresponding fixed version, or if the security update for CVE-2024-29994 has not been installed.

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.

dbcve · scoped
Upgrade available Upgrade to 10.0.17763.5820 / 10.0.19044.4412 / 10.0.19045.4412 or later
Fixed in 10.0.17763.582010.0.19044.441210.0.19045.4412
Interim mitigation

Apply the Microsoft security update for CVE-2024-29994 via Windows Update or enterprise patch management tools to address the vulnerability in the SCSI class driver.

Recommended fix High confidence

Windows Security Update containing CVE-2024-29994 patch for your specific Windows version (10.0.17763.5820, 10.0.19044.4412, 10.0.19045.4412, 10.0.22000.2960, 10.0.22621.3593, 10.0.22631.3593, or 10.0.20348.2461 depending on your OS branch)

  1. Identify the current Windows version by running 'winver' or 'systeminfo' command
  2. Determine which version branch your system belongs to (1809, 21h2, 22h2, or specific Windows 11/Server version)
  3. Apply the appropriate Windows Security Update that contains the fix for CVE-2024-29994
  4. For Windows 10 1809 and Windows Server 2019: Update to version 10.0.17763.5820 or later
  5. For Windows 10 21h2: Update to version 10.0.19044.4412 or later
  6. For Windows 10 22h2: Update to version 10.0.19045.4412 or later
  7. For Windows 11 21h2: Update to version 10.0.22000.2960 or later
  8. For Windows 11 22h2: Update to version 10.0.22621.3593 or later
Caveat Standard Windows update risks apply - ensure backups and test in non-production environment before deploying broadly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29994 — 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-29994 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