dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 Sep 2024.
Windows 10 1507Operating system · Microsoft

CVE-2024-38193

HIGH · 7.8 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 10.0.10240.20751 / 10.0.14393.7259 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Public exploit Zero-click Patch available

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 (AFD.sys), which handles Winsock communications. An authenticated attacker could exploit this to gain elevated privileges on the affected system, potentially executing arbitrary code in kernel context.

MitigationApply the Microsoft security update for CVE-2024-38193. Until patches are deployed, minimize user privileges and monitor for suspicious kernel-mode activity.

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 10 1507Operating system
Affected:< 10.0.10240.20751
Windows 10 1607Operating system
Affected:< 10.0.14393.7259
Windows 10 1809Operating system
Affected:< 10.0.17763.6189
Windows 10 21h2Operating system
Affected:< 10.0.19044.4780
Windows 10 22h2Operating system
Affected:< 10.0.19045.4780
Windows 11 21h2Operating system
Affected:< 10.0.22000.3147
Windows 11 22h2Operating system
Affected:< 10.0.22621.4037
Windows 11 23h2Operating system
Affected:< 10.0.22631.4037

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 installed Windows version
    Open Settings > System > About, or run 'winver' from command prompt, or run 'systeminfo' from command prompt and look at the OS Version line
    Affected if The displayed version/build number is lower than any of the following: Windows 10 1507 build 10240.20751, Windows 10 1607 build 14393.7259, Windows 10 1809 build 17763.6189, Windows 10 21h2 build 19044.4780, Windows 10 22h2 build 19045.4780, Windows 11 21h2 build 22000.3147, Windows 11 22h2 build 22
  2. Confirm AFD.sys driver presence
    Verify that the file C:\Windows\System32\drivers\afd.sys exists on the system
    Affected if The AFD.sys driver file is present (this is the vulnerable component, though version checking in step 1 is the primary determinant of exposure)
  3. Check security update installation status
    Open Settings > Windows Update > Update history, or run 'wmic qfe list' from command prompt to list installed hotfixes, and look for security updates with KB numbers corresponding to the CVE release month
    Affected if The security update for CVE-2024-38193 has not been installed (the system remains unpatched and thus vulnerable if the version falls within the affected range)

A system is affected if it runs a Windows version with a build number lower than the fixed versions listed and the CVE-2024-38193 security update has not been applied.

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
Upgrade available Upgrade to 10.0.10240.20751 / 10.0.14393.7259 / 10.0.17763.6189 or later
Fixed in 10.0.10240.2075110.0.14393.725910.0.17763.6189
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply the Microsoft security update for CVE-2024-38193. Until patches are deployed, minimize user privileges and monitor for suspicious kernel-mode activity.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.20751+ | Windows 10 1607: 10.0.14393.7259+ | Windows 10 1809: 10.0.17763.6189+ | Windows 10 21h2: 10.0.19044.4780+ | Windows 10 22h2: 10.0.19045.4780+ | Windows 11 21h2: 10.0.22000.3147+ | Windows 11 22h2: 10.0.22621.4037+ | Windows 11 23h2: 10.0.22631.4037+

  1. Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify your current Windows version and build number
  2. Identify which version branch your system belongs to from: 1507, 1607, 1809, 21h2, 22h2, 11-21h2, 11-22h2, or 11-23h2
  3. Apply the corresponding Windows security update: For 1507 upgrade to 10.0.10240.20751 or later; for 1607 upgrade to 10.0.14393.7259 or later; for 1809 upgrade to 10.0.17763.6189 or later; for 21h2 upgrade to 10.0.19044.4780 or later; for 22h2 upgrade to 10.0.19045.4780 or later; for Windows 11 21h2 upgrade to 10.0.22000.3147 or later; for Windows 11 22h2 upgrade to 10.0.22621.4037 or later; for Wi
  4. Restart the system after applying the update
  5. Verify successful remediation by running 'winver' and confirming the build number meets or exceeds the target version for your branch
Caveat Standard Windows update risks: update may require restart, potential for compatibility issues with legacy software; test updates in staging environment before production deployment

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

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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