CVE-2023-21768
Windows Ancillary Function Driver for WinSock Elevation of Privilege Vulnerability
- CVSS
- 7.8Highscored by the publisher (CNA)
- Exploited in the wild
- Not knownPublic exploit code; not in CISA KEV
- EPSS
- 65.4%chance of exploitation in the next 30 daystop 0.8% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 10 Jan 2023analysed here 12 Nov 2026
Summary
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Microsoft Windows 11 version 21H2 | >= 10.0.0 and < 10.0.22000.1455Vendor says fixed in: not stated | |
| Microsoft Windows 11 version 22H2 | >= 10.0.22621.0 and < 10.0.22621.1105Vendor says fixed in: not stated | |
| Microsoft Windows Server 2022 | >= 10.0.20348.0 and < 10.0.20348.1487Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- microsoft:windows_11
- microsoft:windows_server_2022
Fix and mitigation
WAF and other mitigations
Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.
Also consider: patch
Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- Yes: 1 Metasploit module · 14 GitHub proofs of concept
- CISA SSVC
- exploitation none, automatable no, technical impact totalAssessed by CISA 8 Oct 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Metasploit
- exploit/windows/local/cve_2023_21768_afd_lpeexploit, rank excellent
GitHub proofs of concept
- chompie1337/Windows_LPE_AFD_CVE-2023-21768511 stars
- SamuelTulach/nullmap203 stars
- Malwareman007/CVE-2023-2176868 stars
- cl4ym0re/cve-2023-21768-compiled27 stars
and 10 more repositories
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 10 Jan 2023Published
- 7 Mar 2023First public exploit or proof of concept55 days later
- 8 Oct 2024CISA SSVC assessment: exploitation none582 days (about 2 years) later
- 1 Jan 2025CVE record last updated84 days (about 3 months) later
- 12 Nov 2026Analysed by vulneraibility.com681 days (about 2 years) later
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | LocalLocal access required (shell, logged-in user). | Local access required (shell, logged-in user). |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | LowThe attacker needs basic user privileges. | The attacker needs basic user privileges. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2023-21768 being exploited?
Not confirmed. CVE-2023-21768 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 65% probability of exploitation in the next 30 days.
How severe is CVE-2023-21768?
CVE-2023-21768 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2023-21768?
Yes. A fix has been recorded for CVE-2023-21768. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2023-21768 affect?
CVE-2023-21768 affects microsoft:windows_11, microsoft:windows_server_2022. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
1 reference in the CVE record, grouped by the tags the record gives them.
Advisories (1)
- msrc.microsoft.com /update-guide/vulnerability/CVE-2023-21768
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Metasploit Framework: exploit and scanner modules
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.