dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-21924

MEDIUM · 5.3 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 →
60/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Workstation Service Remote Protocol Security Feature Bypass 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 Microsoft Windows vulnerability in the Workstation Service remote protocol that allows a security feature bypass. The Workstation Service enables applications to access Windows workstations over the network, and this vulnerability allows attackers to bypass security mechanisms in the remote protocol. The CVSS 5.3 score indicates a medium-severity issue exploitable remotely with low complexity.

MitigationApply the Microsoft security update for CVE-2022-21924 to all affected Windows systems. This is typically delivered through Windows Update or manual security patch deployment.

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:all versions= 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
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Identify Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to see the exact Windows version and build number
    Affected if The version falls within the affected list: Windows 10 (1607, 1809, 1909, 20h2, 21h1, 21h2), Windows 11 all versions, Windows 7 all versions, Windows 8.1, Windows Server 2008/2012/2016 all versions, Windows Server 2012 R2, Windows Server 2022 (20h2), Windows Server 2008 R2
  2. Verify Workstation Service is present
    Open Services console (services.msc) or run 'sc query LanmanWorkstation' to check if the Workstation Service is installed on the system
    Affected if The Workstation Service (service name: LanmanWorkstation) exists on the system - this is the vulnerable component
  3. Confirm Workstation Service is enabled
    Run 'sc queryex type= service state= all' and look for LanmanWorkstation, or check in Services.msc that the service is not disabled
    Affected if The Workstation Service is set to any startup type other than 'Disabled' (Automatic, Manual, or Automatic (Delayed Start))
  4. Check for incoming SMB/RPC listener
    Run 'netstat -an | findstr "445"' or check if TCP port 445 (SMB) is listening, since the Workstation Service handles remote protocol connections over SMB
    Affected if The system is listening on TCP port 445 or has SMB file sharing enabled - this exposes the remote protocol interface

A system is affected if it runs any affected Windows version listed and has the Workstation Service enabled (not disabled), exposing the remote protocol interface to potential exploitation.

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-21924 to all affected Windows systems. This is typically delivered through Windows Update or manual security patch deployment.

Recommended fix Moderate confidence
  1. Identify your Windows version and build (run 'winver' or 'systeminfo').
  2. Open the Microsoft Security Response Center (MSRC) portal at https://portal.msrc.microsoft.com and search for CVE‑2022‑21924 to locate the applicable security update (KB number) for your OS.
  3. Install the security update via Windows Update or manually download it from the Microsoft Update Catalog using the KB number.
  4. Restart the computer to apply the changes.
Caveat May require a restart; no major functional breaking changes known.

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.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-21924 — 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-21924 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