CVE-2022-24539
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 Hyper-V Shared Virtual Hard Disks Information Disclosure 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 an information disclosure vulnerability in Windows Hyper-V's shared virtual hard disk (VHD) feature. The vulnerability allows an attacker to potentially access sensitive information from shared virtual hard disks without proper authorization, due to improper access control in the shared VHD handling code.
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= 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Confirm Windows Server versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify if the server is Windows Server 2016, 2019, or 2022. These are the affected versions.Affected if The server runs Windows Server 2016, 2019, or 2022 (any build).
-
Verify Hyper-V role is installedRun 'Get-WindowsFeature -Name *Hyper-V*' in PowerShell or check 'systeminfo' for Hyper-V. The vulnerability only applies if Hyper-V is present.Affected if The Hyper-V role is installed on the server.
-
Check for shared virtual hard disk configurationRun 'Get-VHD -Path *' to list VHDs, then inspect VM configurations using 'Get-VM | Get-VMHardDiskDrive' looking for Shared volumes or CSV (Cluster Shared Volume) connections. Alternatively, check VM settings in Hyper-V Manager for any VHD set to 'Shared' or examine .vhdx metadata for shared flags.Affected if Any virtual machine is configured with a shared virtual hard disk (VHD set or shared VHDX).
You are affected if your Windows Server 2016/2019/2022 host has Hyper-V installed AND is using shared virtual hard disk configurations for one or more VMs.
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 relevant Microsoft Windows security updates (KB5001402 and related patches for April 2021 and subsequent months) to all Windows hosts running Hyper-V with shared virtual hard disk configurations. Verify shared VHD functionality after patching.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24539 — 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-24539 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