dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-35762

HIGH · 7.8 CVSS v3.1 Published 2022-08-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Storage Spaces Direct 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 an elevation of privilege vulnerability in Microsoft Storage Spaces Direct, a Windows Server feature that enables creating highly available, scalable storage. The vulnerability likely allows a local attacker to gain elevated privileges on affected Windows Server systems.

MitigationApply the Microsoft security updates for CVE-2022-35762. Ensure Storage Spaces Direct deployments are patched in accordance with standard Windows Server patch management cycles.

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 10Operating system
Affected:= 20h2= 21h1= 21h2= 1607= 1809
Windows Server 2016Operating system
Affected:all versions= 20h2
Windows Server 2019Operating system
Affected:all versions
Windows Server 2022Operating system
Affected:all versions

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. Identify Windows version and build
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows version and build number
    Affected if The build number matches Windows 10 versions 1607, 1809, 20h2, 21h1, 21h2; Windows Server 2016 all versions; Windows Server 2019 all versions; Windows Server 2022 all versions; or Windows Server 20h2
  2. Confirm Storage Spaces Direct is installed
    Run 'Get-WindowsOptionalFeature -Online -FeatureName *StorageSpacesDirect*' in PowerShell with admin rights, or check Server Manager for the Storage Spaces Direct role installed
    Affected if Storage Spaces Direct feature is present and enabled on the system
  3. Check if S2D cluster is configured
    Run 'Get-Cluster | Select-Object -Property Name, S2DEnabled' in PowerShell on cluster nodes, or inspect 'Get-ClusterS2D' output to see if S2D cluster exists
    Affected if A Storage Spaces Direct cluster is configured and operational on the system
  4. Verify security update KB5015000 is installed
    Run 'Get-HotFix | Where-Object {$_.HotFixID -eq "KB5015000"}' or check Windows Update history for this specific KB number
    Affected if The security update KB5015000 (or subsequent related updates for this CVE) is NOT installed

A system is affected if it runs a listed Windows 10/Server version, has Storage Spaces Direct enabled or configured as an S2D cluster, and is missing the KB5015000 security update.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Microsoft security updates for CVE-2022-35762. Ensure Storage Spaces Direct deployments are patched in accordance with standard Windows Server patch management cycles.

Recommended fix Moderate confidence
  1. Check current Windows version by running 'winver' or 'systeminfo'
  2. Open Windows Update by searching for 'Check for updates' in the Start menu
  3. Click 'Check for updates' and install all available security updates
  4. Alternatively, manually download the security update from Microsoft Update Catalog for your specific Windows version (KB5015863 for July 2022 or subsequent updates)
  5. Restart the system after installing updates
  6. Verify the update installed successfully by checking Windows Update history

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

Fix this in Windows 10 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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