dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2023-32008

HIGH · 7.8 CVSS v3.1 Published 2023-06-14
Fix available
A fix is available. Upgrade to 10.0.10240.19983 / 10.0.14393.5989 or later.
See remediation →
81/100
Remediation priority · High
No privileges Patch available

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
Windows Resilient File System (ReFS) Remote Code Execution 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
How this class of weakness works · CWE-476

The code follows a pointer that is null, crashing the process. An attacker who can reliably trigger it turns the crash into a denial of service. The fix is checking for null before use and handling the failure path gracefully.

General guidance for the null pointer dereference class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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 1507Operating system
Affected:< 10.0.10240.19983
Windows 10 1607Operating system
Affected:< 10.0.14393.5989
Windows 10 1809Operating system
Affected:< 10.0.17763.4499
Windows 10 21h2Operating system
Affected:< 10.0.19044.3086
Windows 10 22h2Operating system
Affected:< 10.0.19045.3087
Windows 11 21h2Operating system
Affected:< 10.0.22000.2057
Windows 11 22h2Operating system
Affected:< 10.0.22621.1848
Windows Server 2016Operating system
Affected:< 10.0.14393.5989

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

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

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.10240.19983 / 10.0.14393.5989 / 10.0.17763.4499 or later
Fixed in 10.0.10240.1998310.0.14393.598910.0.17763.4499
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Microsoft Windows security update KB5027222 (or version-specific equivalent) - minimum fixed builds: Win10 1507:10.0.10240.19983 | Win10 1607:10.0.14393.5989 | Win10 1809:10.0.17763.4499 | Win10 21h2:10.0.19044.3086 | Win10 22h2:10.0.19045.3087 | Win11 21h2:10.0.22000.2057 | Win11 22h2:10.0.22621.18

  1. Identify the current Windows version by running 'winver' or 'systeminfo' to confirm which version and build number is installed
  2. Navigate to https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-32008 to obtain the specific security update for your Windows version
  3. Apply the corresponding security update through Windows Update (Settings > Update & Security > Windows Update > Check for updates) or by manually downloading the update from the Microsoft Update Catalog
  4. After installation, restart the system to complete the patch process
  5. Verify the patch was successfully applied by checking the installed updates list or running 'systeminfo' to confirm the build number matches or exceeds the fixed version for your product
Caveat Standard Windows monthly security update - minimal risk; always test in staging environment before production deployment

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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