dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-21914

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 Remote Access Connection Manager 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 Windows Remote Access Connection Manager (RasMan service). An authenticated attacker could exploit this to gain higher-level Windows privileges, potentially achieving SYSTEM-level access. The vulnerability exists in how the Remote Access Connection Manager service handles certain operations, allowing a local attacker to escalate their privileges.

MitigationApply the Microsoft security update released for CVE-2022-21914 to all affected Windows systems. Prioritize servers and workstations with direct network exposure or multi-user access.

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 Rt 8.1Operating system
Affected:all versions
Windows ServerOperating system
Affected:= 20h2= 2022
Windows Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2

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. Identify Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the installed Windows version and build number
    Affected if The version matches any of the affected products listed (Windows 10, 11, 7, 8.1, Rt 8.1, or Windows Server 2008/2012/2016/2019/2020/2022)
  2. Confirm RasMan service presence
    Run 'sc query RasMan' or check the Windows Services list for 'Remote Access Connection Manager' service
    Affected if The RasMan service exists on the system (this service is present by default on most Windows installations)
  3. Check RasMan service status
    Run 'sc query RasMan' to see if the service is running, stopped, or disabled
    Affected if The RasMan service is set to run (even if currently stopped, the vulnerability applies when the service can be started)
  4. Verify security update installation
    Run 'wmic qfe list' or check Windows Update history for the security update corresponding to CVE-2022-21914 (typically released in January 2022 or later)
    Affected if The specific CVE-2022-21914 security update is NOT installed on the system

A system is affected if it runs a vulnerable Windows version from the affected list AND has the RasMan service available AND is missing the CVE-2022-21914 security update.

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 released for CVE-2022-21914 to all affected Windows systems. Prioritize servers and workstations with direct network exposure or multi-user access.

Recommended fix High confidence

Apply the January 2022 Security Updates (KB5009557 or later) from Microsoft Update Catalog

  1. Open Windows Update on the affected system (Settings > Update & Security > Windows Update)
  2. Click 'Check for updates' to download and install the latest security updates
  3. If automatic updates are disabled, manually search for and install KB5009557 (January 2022 security update) or subsequent relevant updates
  4. Restart the system after installing updates
  5. Verify the update was installed by checking Installed Updates in Control Panel > Programs and Features
Caveat Standard patching carries minimal risk; ensure backups exist before applying updates to production systems

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-21914 — 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-21914 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