cve.bz

CVE-2023-21712 microsoft: Race Condition

8.1 highEPSS 1.0%Fix available

High (8.1) in microsoft. EPSS 1.0% estimated probability of exploitation activity in the next 30 days.

On this page
Windows Point-to-Point Tunneling Protocol Remote Code Execution Vulnerability

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
1.0% (unchanged from 1.0% a week ago; 1.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 63rd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2024-10-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-21712 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-21712?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-21712?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-21712 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.3650
Microsoft Windows 10 Version 1809from 10.0.0 before 10.0.17763.3650
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.3650
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.3650
Microsoft Windows 10 Version 21H1from 10.0.0 before 10.0.19043.2251
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.1249
Microsoft Windows 10 Version 20H2from 10.0.0 before 10.0.19042.2251
Microsoft Windows 11 version 21H2from 10.0.0 before 10.0.22000.1219
Microsoft Windows 10 Version 21H2from 10.0.19043.0 before 10.0.19044.2251
Microsoft Windows 11 version 22H2from 10.0.22621.0 before 10.0.22621.819
Microsoft Windows 10 Version 22H2from 10.0.19045.0 before 10.0.19045.2486
Microsoft Windows 10 Version 1507from 10.0.10240.0 before 10.0.10240.19562
Microsoft Windows 10 Version 1607from 10.0.14393.0 before 10.0.14393.5501
Microsoft Windows Server 2016from 10.0.14393.0 before 10.0.14393.5501
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before 10.0.14393.5501
Microsoft Windows 8.1from 6.3.0 before 6.3.9600.20671
Microsoft Windows Server 2012from 6.2.9200.0 before 6.2.9200.23968
Microsoft Windows Server 2012 (Server Core installation)from 6.2.9200.0 before 6.2.9200.23968
Microsoft Windows Server 2012 R2from 6.3.9600.0 before 6.3.9600.20671
Microsoft Windows Server 2012 R2 (Server Core installation)from 6.3.9600.0 before 6.3.9600.20671

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON