cve.bz

CVE-2023-21728 microsoft: Uncontrolled Resource Consumption

7.5 highEPSS 2.1%

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

On this page
Windows Netlogon Denial of Service Vulnerability

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
2.1% (unchanged from 2.1% a week ago; 2.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 82nd 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: yes · Technical impact: partial, assessed 2024-07-16. 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-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2023-21728 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-21728?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-21728?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-21728 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.3887
Microsoft Windows 10 Version 1809from 10.0.0 before 10.0.17763.3887
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.3887
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.3887
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.1487
Microsoft Windows 10 Version 20H2from 10.0.0 before 10.0.19042.2486
Microsoft Windows 11 version 21H2from 10.0.0 before 10.0.22000.1455
Microsoft Windows 10 Version 21H2from 10.0.19043.0 before 10.0.19044.2486
Microsoft Windows 11 version 22H2from 10.0.22621.0 before 10.0.22621.1105
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.19685
Microsoft Windows 10 Version 1607from 10.0.14393.0 before 10.0.14393.5648
Microsoft Windows Server 2016from 10.0.14393.0 before 10.0.14393.5648
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before 10.0.14393.5648
Microsoft Windows 7from 6.1.0 before 6.1.7601.26321
Microsoft Windows 7 Service Pack 1from 6.1.0 before 6.1.7601.26321
Microsoft Windows 8.1from 6.3.0 before 6.3.9600.20778
Microsoft Windows Server 2008 Service Pack 2from 6.0.6003.0 before 6.0.6003.21872
Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)from 6.0.6003.0 before 6.0.6003.21872
Microsoft Windows Server 2008 Service Pack 2from 6.0.6003.0 before 6.0.6003.21872
Microsoft Windows Server 2008 R2 Service Pack 1from 6.1.7601.0 before 6.1.7601.26321
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)from 6.1.7601.0 before 6.1.7601.26321
Microsoft Windows Server 2012from 6.2.9200.0 before 6.2.9200.24075
Microsoft Windows Server 2012 (Server Core installation)from 6.2.9200.0 before 6.2.9200.24075
Microsoft Windows Server 2012 R2from 6.3.9600.0 before 6.3.9600.20778
Microsoft Windows Server 2012 R2 (Server Core installation)from 6.3.9600.0 before 6.3.9600.20778

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

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

References

Check your stackJSON