CVE-2022-22039
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 Network File System 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 · moderate confidenceA Remote Code Execution vulnerability in Windows Network File System (NFS) service. The NFS server component in Windows fails to properly handle certain network requests, allowing an unauthenticated attacker to execute arbitrary code by sending specially crafted packets to the target system.
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= 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
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Windows Server versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the exact Windows Server version and build numberAffected if The version is Windows Server 2008 (any edition), Server 2012 (any edition), Server 2016, Server 2019, or Server 2022
-
Verify NFS Server role is installedRun 'Get-WindowsFeature -Name *NFS*' in PowerShell or check via Server Manager > Add Roles and Features > File Services > Server for NFSAffected if The NFS Server role (File Services role) is installed on the system
-
Confirm NFS service is runningRun 'Get-Service -Name NFS*' or 'services.msc' and look for 'NFS Server' service with statusAffected if The NFS Server service (nfs service) exists and is in a Running state
-
Check for applied security updateRun 'Get-HotFix | Where-Object {$_.HotFixID -eq "KB5011553"}' or view installed updates via 'appwiz.cpl' and look for KB5011553 or later security updatesAffected if KB5011553 or a subsequent security update is NOT installed (the system is unpatched)
A system is affected if it runs a vulnerable Windows Server version (2008/2012/2016/2019/2022) AND has the NFS Server role installed with the service running AND is missing the KB5011553 security update.
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 security update (KB5011553 or subsequent) and ensure NFS services are properly firewalled to restrict access to trusted networks only.
- 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-22039 — 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-22039 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