dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-21858

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 Bind Filter 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 a local privilege escalation vulnerability in the Windows Bind Filter Driver. An authenticated attacker could exploit this to elevate from a standard user account to SYSTEM-level privileges by interacting with the vulnerable driver.

MitigationApply the relevant Windows security update for CVE-2022-21858, which patches the Bind Filter Driver vulnerability. In enterprise environments, deploy the update through standard patch management processes after testing.

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:= 20h2= 21h1= 21h2= 1809= 1909
Windows 11Operating system
Affected:all versions
Windows ServerOperating system
Affected:= 20h2= 2022
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
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 build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number (e.g., 19043.1288)
    Affected if The build number falls outside the patched builds for your Windows version (the specific patched build varies by Windows version and release channel)
  2. Identify Windows release version
    Run 'ver' at command prompt or check the Windows version via Settings > System > About to determine if you are on 1809, 1909, 20h2, 21h1, 21h2, 11, Server 2019, or Server 20h2/2022
    Affected if Your Windows release matches one listed in the affected products (1809, 1909, 20h2, 21h1, 21h2, Windows 11 any version, Server 2019 any version, Server 20h2, or Server 2022)
  3. Check Bind Filter Driver presence
    Run 'fltmc filters' at an elevated command prompt to list loaded filter drivers, or check the driver file existence at %SystemRoot%\System32\drivers\bindflt.sys
    Affected if The Bind Filter Driver (bindflt.sys) is loaded or present on the system - this driver contains the vulnerable code path
  4. Verify patch installation status
    Run 'powershell "Get-HotFix -Description "Security Update" | Where-Object {$_.HotFixID -eq "KB5001402" -or $_.HotFixID -eq "KB5000802"}'" to check for the CVE-2022-21858 security update (exact KB varies by Windows version)
    Affected if The security update for CVE-2022-21858 is NOT installed - the system remains vulnerable

A user is affected if they run an unpatched Windows version from the affected list (1809, 1909, 20h2, 21h1, 21h2, Windows 11, Server 2019, Server 20h2, or Server 2022) and the Bind Filter Driver is present without the corresponding security update installed.

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 relevant Windows security update for CVE-2022-21858, which patches the Bind Filter Driver vulnerability. In enterprise environments, deploy the update through standard patch management processes after testing.

Recommended fix Moderate confidence

Apply the relevant Windows security update for CVE-2022-21858 (check msrc.microsoft.com for the specific KB number for your Windows version)

  1. Identify the applicable security update for CVE-2022-21858 from the Microsoft Security Response Center (msrc.microsoft.com)
  2. Open Windows Settings > Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the relevant security update
  4. Alternatively, download the update from the Microsoft Update Catalog using the specific KB number for this CVE
  5. Restart the system after applying the update
  6. Verify the update is installed by checking installed updates or using the 'systeminfo' command

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
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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