CVE-2022-24484
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 · uneditedWindows Cluster Shared Volume (CSV) Denial of Service 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 confidenceThis is a denial of service vulnerability in Windows Cluster Shared Volume (CSV) functionality. An authenticated attacker could exploit this to cause a denial of service condition on affected Windows Server systems running CSV. The medium severity reflects the limited scope of impact (DoS only, requires authentication).
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 dataall versions= r2all versions= 20h2all versionsall versionsCVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Windows Server versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' from an elevated command prompt to determine the exact Windows Server version and build number.Affected if The installed version matches Windows Server 2012, 2012 R2, 2016, 20H2, 2019, or 2022.
-
Verify if the system is configured as a failover clusterRun 'Get-Cluster' from PowerShell (requires Failover Clustering module) or check the Failover Clustering feature status in Server Manager under 'Add roles and features'.Affected if The system is a member of a failover cluster or has the Failover Clustering feature installed.
-
Determine if Cluster Shared Volumes (CSV) is enabledRun 'Get-ClusterSharedVolume -Cluster <clustername>' in PowerShell on a cluster node, or inspect the cluster object in Failover Cluster Manager under 'Cluster Shared Volumes'.Affected if One or more CSV volumes are present and online on the cluster.
-
Confirm the specific build number is within the affected rangeRun 'winver' or 'systeminfo' to obtain the full build number (e.g., 10.0.14393 for Windows Server 2016). Compare against Microsoft's official CVE-2022-24484 bulletin for the exact build numbers addressed by the security update.Affected if The build number is earlier than the security update patch level for the respective Windows Server version.
The system is affected if it runs an affected Windows Server version (2012 through 2022), is configured as part of a failover cluster, and has Cluster Shared Volumes (CSV) enabled, with a build number predating the CVE-2022-24484 security patch.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the Microsoft security update for CVE-2022-24484 to all affected Windows Server systems running Cluster Shared Volumes, following proper failover clustering maintenance procedures.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-24484 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-24484 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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