Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET
.NET NuGet
CISA KEV · ACTIVELY EXPLOITED
HIGH severity

CVE-2023-38180

HIGH

CVE-2023-38180 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in Microsoft.AspNetCore.App.Runtime.win-arm64. It is in CISA's Known Exploited Vulnerabilities catalog (added 2023-08-09) — treat it as actively exploited and patch now. O3 Security confirms whether CVE-2023-38180 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

.NET Denial of Service Vulnerability

Also known asBIT-aspnet-core-2023-38180BIT-dotnet-2023-38180BIT-dotnet-sdk-2023-38180GHSA-vmch-3w2x-vhgq
Published
Aug 8, 2023
Updated
Aug 12, 2026
Affected
9 pkgs
Patched
9 / 9
Exploits
2 known
Exploitation data as of Aug 28, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

  • Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2023-08-09. Federal agencies were required to remediate by 2023-08-30.
  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2023-38180.

EPSS Exploitation Probability

via FIRST.org ↗
14.0%probability of exploitation in next 30 days
Moderate Risk-0.67%
Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk
0.00%6.64%13.3%19.9%0.9%14.0%Feb 26Jun 26Aug 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2023-38180 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 0 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

9 pkgs affected
.NETMicrosoft.AspNetCore.App.Runtime.win-arm64.NETMicrosoft.AspNetCore.App.Runtime.win-x64.NETMicrosoft.AspNetCore.App.Runtime.win-x86.NETMicrosoft.AspNetCore.Server.Kestrel.Transport.Libuv.NETMicrosoft.AspNetCore.App.Runtime.win-arm64.NETMicrosoft.AspNetCore.App.Runtime.win-x64.NETMicrosoft.AspNetCore.App.Runtime.win-x86.NETMicrosoft.AspNetCore.Server.Kestrel.Transport.Libuv+1 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

.NET and Visual Studio Denial of Service Vulnerability

Affected Packages

9 total 9 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.AspNetCore.App.Runtime.win-arm647.0.0&&< 7.0.107.0.10
.NETNuGetMicrosoft.AspNetCore.App.Runtime.win-x647.0.0&&< 7.0.107.0.10
.NETNuGetMicrosoft.AspNetCore.App.Runtime.win-x867.0.0&&< 7.0.107.0.10
.NETNuGetMicrosoft.AspNetCore.Server.Kestrel.Transport.Libuv6.0.0&&< 6.0.216.0.21
.NETNuGetMicrosoft.AspNetCore.App.Runtime.win-arm646.0.0&&< 6.0.216.0.21
.NETNuGetMicrosoft.AspNetCore.App.Runtime.win-x646.0.0&&< 6.0.216.0.21
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.AspNetCore.App.Runtime.win-arm64. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update Microsoft.AspNetCore.App.Runtime.win-arm64 to 7.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-38180 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2023-38180 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-38180. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Frequently Asked Questions

.NET and Visual Studio Denial of Service Vulnerability
O3 Security · Impact-Aware SCA

Is CVE-2023-38180 in your dependencies?

O3 detects CVE-2023-38180 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

CVE-2023-38180: .NET Denial of Service… | O3 Security