CVE-2023-32011

Windows iSCSI Discovery Service Denial of Service Vulnerability

HIGH
7.5
CVSS Score
Published: June 13, 2023 at 11:26 PM UTC
Updated: June 17, 2026 at 05:57 AM UTC
12 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows Server 2012

Using Windows 10 Version 1809 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1809 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 2%
SSVC
No known exploit

Description

Windows iSCSI Discovery Service Denial of Service Vulnerability

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 10.0.10240.1998310.0.10240.0 ≤ v < 10.0.10240.1998310.0.10240.0
Affected range stops below 10.0.10240.19983, so it looks safe — our inference, not a vendor statement
v < 10.0.14393.598910.0.14393.0 ≤ v < 10.0.14393.598910.0.14393.0
Affected range stops below 10.0.14393.5989, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.449910.0.0 ≤ v < 10.0.17763.449910.0.17763.0 ≤ v < 10.0.17763.449910.0.010.0.17763.0
Affected range stops below 10.0.17763.4499, so it looks safe — our inference, not a vendor statement
v < 10.0.19044.308610.0.19043.0 ≤ v < 10.0.19044.308610.0.19043.0
Affected range stops below 10.0.19044.3086, so it looks safe — our inference, not a vendor statement
v < 10.0.19045.308710.0.19045.0 ≤ v < 10.0.19045.308610.0.19045.0
Affected range stops below 10.0.19045.3086, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.19045.3087, so it looks safe — our inference, not a vendor statement
v < 10.0.22000.205710.0.0 ≤ v < 10.0.22000.205710.0.0
Affected range stops below 10.0.22000.2057, so it looks safe — our inference, not a vendor statement
v < 10.0.22621.184810.0.22621.0 ≤ v < 10.0.22621.184810.0.22621.0
Affected range stops below 10.0.22621.1848, so it looks safe — our inference, not a vendor statement
6.0.6003.0 ≤ v < 6.0.6003.221136.1.7601.0 ≤ v < 6.1.7601.265646.0.6003.06.1.7601.0r2 sp1sp2
Affected range stops below 6.0.6003.22113, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.7601.26564, so it looks safe — our inference, not a vendor statement
6.2.9200.0 ≤ v < 6.2.9200.243146.3.9600.0 ≤ v < 6.3.9600.210136.2.9200.06.3.9600.0r2
Affected range stops below 6.2.9200.24314, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.3.9600.21013, so it looks safe — our inference, not a vendor statement
v < 10.0.14393.598910.0.14393.0 ≤ v < 10.0.14393.598910.0.14393.0
Affected range stops below 10.0.14393.5989, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-125NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card