CVE-2023-38171

Microsoft QUIC Denial of Service Vulnerability

HIGH
7.5
CVSS Score
Published: October 10, 2023 at 05:07 PM UTC
Updated: June 17, 2026 at 06:09 AM UTC
7 products affected across 1 vendorWindows Server 2022Windows 11 22H2Visual Studio 2022

Using Microsoft Visual Studio 2022 version 17.2 by Microsoft?

Get instant alerts when new vulnerabilities affect Microsoft Visual Studio 2022 version 17.2 - before attackers find them.

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

Description

Microsoft QUIC Denial of Service Vulnerability

Affected

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

7.0.0 ≤ v < 7.0.127.0.0 ≤ v < 7.0.137.0.0
Affected range stops below 7.0.12, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.0.13, so it looks safe — our inference, not a vendor statement
7.3.0 ≤ v < 7.3.97.3.0
Affected range stops below 7.3.9, so it looks safe — our inference, not a vendor statement
17.6.0 ≤ v < 17.6.917.7.0 ≤ v < 17.7.6
Affected range stops below 17.6.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.7.6, so it looks safe — our inference, not a vendor statement
17.2.0 ≤ v < 17.2.2017.2.0 ≤ v < 17.2.2117.4.0 ≤ v < 17.4.1217.4.0 ≤ v < 17.4.1317.6.0 ≤ v < 17.6.817.6.0 ≤ v < 17.6.917.7.0 ≤ v < 17.7.517.7.0 ≤ v < 17.7.617.2.017.4.017.6.017.7.0
Affected range stops below 17.2.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.2.21, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.4.12, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.4.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.6.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.6.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.7.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.7.6, so it looks safe — our inference, not a vendor statement
v < 10.0.22621.242810.0.22621.0 ≤ v < 10.0.22621.242810.0.22621.0
Affected range stops below 10.0.22621.2428, so it looks safe — our inference, not a vendor statement
10.0.20348.0 ≤ v < 10.0.20348.203110.0.20348.0
Affected range stops below 10.0.20348.2031, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < 10.0.22000.253810.0.0
Affected range stops below 10.0.22000.2538, 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 exploitAutomatablePartial impact

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

CVSS

7.5HIGHmicrosoft
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-476NVD-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