dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-24507

HIGH · 7.8 CVSS v3.1 Published 2022-03-09
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 Ancillary Function Driver for WinSock 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 Elevation of Privilege vulnerability in the Windows Ancillary Function Driver for WinSock (AFD.sys). An authenticated attacker with local access can exploit this to gain higher privileges on the affected system, potentially achieving SYSTEM-level access.

MitigationApply the Microsoft security update (KB5001402 or subsequent relevant patches) to address this vulnerability. Prioritize patching domain controllers and systems with sensitive data or external exposure.

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= 1607= 1809= 1909
Windows 11Operating system
Affected:all versions
Windows ServerOperating system
Affected:= 20h2
Windows Server 2016Operating system
Affected:all versions
Windows Server 2019Operating system
Affected:all versions
Windows Server 2022Operating 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. Identify Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to retrieve the installed Windows version and build number
    Affected if The version matches Windows 10 (20h2, 21h1, 21h2, 1607, 1809, or 1909), Windows 11 any version, Windows Server 20h2, Windows Server 2016, Windows Server 2019, or Windows Server 2022
  2. Check AFD.sys file version
    Locate AFD.sys in C:\Windows\System32\drivers\ and view its Properties > Details to see the File Version, or run 'powershell (Get-Item C:\Windows\System32\drivers\afd.sys).VersionInfo.FileVersion'
    Affected if The AFD.sys version corresponds to an unpatched build of the affected Windows versions listed (specific vulnerable versions can be cross-referenced with Microsoft KB5001402 release notes)
  3. Verify patch installation status
    Run 'powershell Get-HotFix -Description "Security Update" | Sort-Object InstalledOn -Descending | Select-Object -First 10' or check for KB5001402 specifically with 'powershell Get-HotFix -Id KB5001402'
    Affected if The security update KB5001402 or subsequent related patches are NOT installed, meaning the system remains vulnerable
  4. Confirm local authentication capability
    Verify the presence of local user accounts that could exploit this flaw by running 'net user' to enumerate local users, noting that any authenticated local user account could potentially leverage this vulnerability
    Affected if An authenticated local user exists on the system (which is typical for Windows installations) and the unpatched version conditions above are met

A user is affected if the system runs any of the listed Windows 10, 11, or Windows Server versions and lacks the KB5001402 or subsequent security patches for AFD.sys.

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 (KB5001402 or subsequent relevant patches) to address this vulnerability. Prioritize patching domain controllers and systems with sensitive data or external exposure.

Recommended fix High confidence

February 2022 Windows Security Updates (KB5010342, KB5010347, KB5010348, KB5010354, KB5010349, or KB5010351 depending on version)

  1. Open Settings on the Windows system and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to ensure the system connects to Windows Update
  3. Install the February 2022 security updates (or later) which contain the fix for CVE-2022-24507
  4. Alternatively, manually download the specific KB update for your Windows version from the Microsoft Update Catalog: search for KB5010342 (Windows 10 20h2/21h1/21h2), KB5010347 (Windows 10 1607), KB5010348 (Windows 11), KB5010354 (Windows Server 2022), KB5010349 (Windows Server 2016), or KB5010351 (Windows Server 2019)
  5. Restart the system after installing the update
  6. Verify the update was installed successfully by checking 'View update history' in Windows Update settings
Caveat Standard Windows security update with no expected breaking changes; as with any system update, test in a non-production environment first if possible

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

Fix this in Windows 10 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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