dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-24491

CRITICAL · 9.8 CVSS v3.1 Published 2022-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Windows 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 confidence

This is a critical remote code execution vulnerability in Windows Network File System (NFS) service. The vulnerability allows remote attackers to execute arbitrary code on affected Windows systems without authentication, likely through specially crafted NFS requests.

MitigationApply the Microsoft security updates for CVE-2022-24491 immediately. If patches are unavailable, consider disabling NFS or restricting network access to trusted hosts.

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:all versions= 20h2= 21h1= 21h2= 1607= 1809= 1909
Windows 11Operating system
Affected:all versions
Windows 8.1Operating system
Affected:all versions
Windows Rt 8.1Operating system
Affected:all versions
Windows Server 2012Operating system
Affected:all versions= r2
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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Windows version is in the affected product list
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to confirm the Windows version. Check against the affected versions: Windows 10 (all versions, specifically 20h2, 21h1, 21h2, 1607, 1809, 1909), Windows 11 (all versions), Windows 8.1 (all versions), Windows Rt 8.1 (all versions), Windows Server 2012 (all versions, R2), Windows Server 2016 (all versions, 20h2), Windows Server 2019 (all versions), Windows Server 2022 (all versions).
    Affected if The installed Windows version matches any of the affected versions listed in the CVE.
  2. Confirm NFS feature is installed on the system
    Run 'Get-WindowsOptionalFeature -Online -FeatureName *NFS*' in PowerShell with admin rights, or check via Programs and Features > Turn Windows features on or off > Services for NFS. Look for 'Services for NFS' or 'NFS' in the feature list.
    Affected if The NFS feature (Services for NFS) is installed or enabled on the system.
  3. Verify the NFS service is running
    Run 'Get-Service -Name *NFS*' or 'sc query nfsservice' in Command Prompt. Check the status of services named 'NFS' or 'Ntfs', or look for 'nfsd.exe' in running processes via Task Manager.
    Affected if The NFS service is present and running on the system.
  4. Check for exposed NFS network listeners
    Run 'netstat -an | findstr "2049"' to check if port 2049 (NFS default port) is listening. Also verify firewall rules allow NFS traffic with 'netsh advfirewall firewall show rule name=all | findstr /i nfs'.
    Affected if Port 2049 is open and listening, or NFS traffic is permitted through the firewall.

A system is potentially affected if it runs an affected Windows version AND has the NFS feature installed and the NFS service is exposed on the network.

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-24491 immediately. If patches are unavailable, consider disabling NFS or restricting network access to trusted hosts.

Recommended fix High confidence
  1. Identify the exact Windows version and build number by running 'winver' or 'systeminfo'
  2. Open Windows Update and check for the February 2022 security updates, or visit the Microsoft Update Catalog
  3. Search for and install the February 2022 security update that includes CVE-2022-24491. For most systems this will be KB5001402 or the equivalent monthly rollup
  4. Restart the system after applying the update
  5. Verify the update was installed successfully by checking Windows Update history or running 'Get-HotFix' in PowerShell
  6. Confirm the NFS service is properly running post-update
Caveat Applying security updates carries minimal risk but should be tested in a non-production environment first; some organizations delay updates due to compatibility concerns

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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