dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-21834

HIGH · 7.8 CVSS v3.1 Published 2022-01-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 User-mode Driver Framework Reflector Driver Elevation of Privilege 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 an elevation of privilege vulnerability in the Windows User-Mode Driver Framework (UMDF) Reflector Driver. The UMDF Reflector allows user-mode drivers to interface with kernel-mode components, and the vulnerability could allow a local attacker to execute code with elevated privileges.

MitigationApply the Microsoft security update (KB5001402 or subsequent patches) that addresses this vulnerability. This is a Windows OS-level patch that should be deployed according to standard patch management procedures.

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 7Operating system
Affected:all versions
Windows 8.1Operating system
Affected:all versions
Windows ServerOperating system
Affected:= 20h2= 2022
Windows Server 2008Operating system
Affected:= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the installed Windows version
    Affected if The version matches Windows 10 (20h2, 21h1, 21h2, 1607, 1809, 1909), Windows 11, Windows 7, Windows 8.1, Windows Server 20h2/2022, Windows Server 2008 R2, Windows Server 2012/2012 R2, or Windows Server 2016
  2. Verify security update is installed
    Open Control Panel > Programs > View installed updates, or run 'powershell "Get-HotFix -Id KB5001402"' to check for this specific patch
    Affected if The KB5001402 update (or a subsequent security patch for this CVE) is NOT installed on the system
  3. Check UMDF Reflector driver presence
    Check for the presence of umdf reflector driver files: navigate to C:\Windows\System32\drivers\ and look for 'WudfRd.sys' or 'UMDF reflector' driver entries in the registry at HKLM\SYSTEM\CurrentControlSet\Services\WudfRd
    Affected if The UMDF Reflector driver (WudfRd.sys) exists on the system and the system is running an affected Windows version without the security patch

The system is affected if it runs an affected Windows version (10, 11, 7, 8.1, Server 2012/2016/2008 R2) and lacks the KB5001402 security update or subsequent patch for this CVE.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Microsoft security update (KB5001402 or subsequent patches) that addresses this vulnerability. This is a Windows OS-level patch that should be deployed according to standard patch management procedures.

Fix this in Windows 10 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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