Threats / Microsoft / CVE-2023-38180
CVE-2023-38180
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft .NET Core and Visual Studio vulnerability
An unspecified denial-of-service vulnerability in Microsoft .NET Core and Visual Studio allows attackers to disrupt service availability.
Verdict
Today item — known-exploited.
This DoS vulnerability in widely-used development and runtime platforms poses availability risk to organizations running affected .NET Core and Visual Studio versions. Active exploitation in the wild increases urgency of patching.
CISA KEV Yes · 2023-08-095EPSS 0.14688 (verify live)6CVSS 7.53CISA SSVC Exploitation: active · Automatable: yes · Impact: partial4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-08-09).
Probability (EPSS)
EPSS 0.14688 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C) · Affected: Microsoft, .NET Core and Visual Studio. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1 day after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft or send malicious input designed to trigger resource exhaustion in the .NET Core runtime or Visual Studio process.
Business
Development teams experience build failures, IDE crashes, or application downtime, disrupting software delivery pipelines and developer productivity.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the vulnerability to crash running .NET applications or development environments, forcing service restarts.
Business
Production .NET applications become unavailable, resulting in service interruptions and potential revenue loss for dependent business operations.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05