dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-21993

HIGH · 7.5 CVSS v3.1 Published 2022-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 Services for NFS ONCRPC XDR Driver 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 confidence

An information disclosure vulnerability in the Windows Services for NFS ONCRPC XDR Driver allows attackers to potentially read sensitive data from memory or gain unauthorized access to NFS-related information. The vulnerability exists in the XDR (External Data Representation) driver component used by the ONC RPC (Open Network Computing Remote Procedure Call) protocol in Windows NFS services.

MitigationApply the Microsoft security update for CVE-2022-21993 to patch the Windows Services for NFS component, or disable the NFS service if not required in the environment.

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 ServerOperating system
Affected:= 20h2= 2022
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:all versions
Windows Server 2019Operating 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 if NFS service is installed and enabled
    Open PowerShell and run: Get-Service -Name *NFS* | Select-Object Name, Status, StartType
    Affected if The NFS service (such as 'NfsServer' or 'NFS' services) is present and running, meaning the vulnerable XDR driver component is active in the environment
  2. Confirm Windows version falls within affected range
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' and compare against: Windows 10 (versions 1607, 1809, 1909, 20h2, 21h1, 21h2), Windows 11 all versions, Windows 8.1 all versions, Windows Rt 8.1 all versions, Windows Server 2012 all versions, Windows Server 2012 R2, Windows Server 2016 all versions, Windows Server 2019 all versions, Windows Server 20h2, Windows Server 2022
    Affected if The installed Windows version matches one of the listed affected versions, placing the system within the vulnerable version range
  3. Check if the security update has been applied
    Open PowerShell and run: Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10 to list recently installed security updates, or check Windows Update history for recent NFS-related patches
    Affected if No recent security updates addressing CVE-2022-21993 have been installed, indicating the system may remain unpatched and vulnerable

The system is potentially affected if the NFS service is enabled, the Windows version is among the listed affected versions, and the corresponding security patch for this vulnerability has not been applied.

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 update for CVE-2022-21993 to patch the Windows Services for NFS component, or disable the NFS service if not required in the environment.

Recommended fix Moderate confidence
  1. Open Windows Update settings on the affected system
  2. Check for and install all available security updates
  3. Ensure the Windows Services for NFS component is updated as part of the security patch
  4. Restart the system if prompted after updates are applied
  5. Verify the installed updates include the CVE-2022-21993 fix by checking the update history

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

Fix this in Windows 10 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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 locally
dbcve dependency scanner

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