# CVE-2023-38180: Microsoft .NET Core and Visual Studio Denial-of-Service

> Attackers can cause a denial of service in .NET and Visual Studio environments, requiring users to apply vendor patches.

- **Severity:** High 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`)
- **Exploited in the wild:** Yes, since 9 Aug 2023 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Aug 2023
- **Updated:** 10 Aug 2026
- **Also known as:** BIT-aspnet-core-2023-38180, BIT-dotnet-2023-38180, BIT-dotnet-sdk-2023-38180, CLEANSTART-2025-MR09563, GHSA-vmch-3w2x-vhgq, UBUNTU-CVE-2023-38180

## What is CVE-2023-38180?

CVE-2023-38180 is a high-severity denial of service vulnerability in Fedoraproject Fedora, published on 8 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

.NET and Visual Studio Denial of Service Vulnerability

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2023-38180?

21 open source packages ship an affected version, including Microsoft.AspNetCore.App.Runtime.win-arm64, aspnet-core and dotnet. It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Microsoft.AspNetCore.App.Runtime.win-arm64` | NuGet | From 6.0.0 | 6.0.21 |
| `Microsoft.AspNetCore.App.Runtime.win-arm64` | NuGet | From 6.0.0 | 6.0.21 |
| `Microsoft.AspNetCore.App.Runtime.win-arm64` | NuGet | From 7.0.0 | 7.0.10 |
| `Microsoft.AspNetCore.App.Runtime.win-arm64` | NuGet | From 7.0.0 | 7.0.10 |
| `aspnet-core` | Bitnami | From 2.1.0 | 2.1.40 |
| `dotnet` | Bitnami | From 6.0.0 | 6.0.21, 7.0.10 |
| `dotnet-sdk` | Bitnami | From 6.0.0 | 6.0.21, 7.0.10 |
| `Microsoft.AspNetCore.App.Runtime.win-x64` | NuGet | From 6.0.0 | 6.0.21 |
| `Microsoft.AspNetCore.App.Runtime.win-x64` | NuGet | From 6.0.0 | 6.0.21 |
| `Microsoft.AspNetCore.App.Runtime.win-x64` | NuGet | From 7.0.0 | 7.0.10 |
| `Microsoft.AspNetCore.App.Runtime.win-x64` | NuGet | From 7.0.0 | 7.0.10 |
| `Microsoft.AspNetCore.App.Runtime.win-x86` | NuGet | From 6.0.0 | 6.0.21 |
| `Microsoft.AspNetCore.App.Runtime.win-x86` | NuGet | From 6.0.0 | 6.0.21 |
| `Microsoft.AspNetCore.App.Runtime.win-x86` | NuGet | From 7.0.0 | 7.0.10 |
| `Microsoft.AspNetCore.App.Runtime.win-x86` | NuGet | From 7.0.0 | 7.0.10 |
| `Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv` | NuGet | All versions | 2.1.40 |
| `Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv` | NuGet | All versions | 2.1.40 |
| `Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv` | NuGet | From 6.0.0 | 6.0.21 |
| `Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv` | NuGet | From 6.0.0 | 6.0.21 |
| `Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets` | NuGet | All versions | 2.1.40 |
| `Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets` | NuGet | All versions | 2.1.40 |

Products: Fedoraproject Fedora, Microsoft .Net, Microsoft Asp.net Core, Microsoft Visual Studio 2022.

## How do I fix CVE-2023-38180?

Upgrade Microsoft.AspNetCore.App.Runtime.win-arm64 to a fixed version for your release line: 6.0.21 or 7.0.10. US federal agencies must fix it by 30 Aug 2023.

## Is CVE-2023-38180 being exploited?

Yes. Attackers have exploited CVE-2023-38180 in the wild since at least 9 Aug 2023.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-38180 and fix it if it is affected.

What it is: CVE-2023-38180 is a high-severity denial of service vulnerability in Fedoraproject Fedora, published on 8 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-38180 in the wild since at least 9 Aug 2023.

Affected packages and fixed versions:
- Microsoft.AspNetCore.App.Runtime.win-arm64 (NuGet): affected from 6.0.0; fixed in 6.0.21
- Microsoft.AspNetCore.App.Runtime.win-arm64 (NuGet): affected from 6.0.0; fixed in 6.0.21
- Microsoft.AspNetCore.App.Runtime.win-arm64 (NuGet): affected from 7.0.0; fixed in 7.0.10
- Microsoft.AspNetCore.App.Runtime.win-arm64 (NuGet): affected from 7.0.0; fixed in 7.0.10
- aspnet-core (Bitnami): affected from 2.1.0; fixed in 2.1.40
- dotnet (Bitnami): affected from 6.0.0; fixed in 6.0.21, 7.0.10
- dotnet-sdk (Bitnami): affected from 6.0.0; fixed in 6.0.21, 7.0.10
- Microsoft.AspNetCore.App.Runtime.win-x64 (NuGet): affected from 6.0.0; fixed in 6.0.21
- Microsoft.AspNetCore.App.Runtime.win-x64 (NuGet): affected from 6.0.0; fixed in 6.0.21
- Microsoft.AspNetCore.App.Runtime.win-x64 (NuGet): affected from 7.0.0; fixed in 7.0.10
- Microsoft.AspNetCore.App.Runtime.win-x64 (NuGet): affected from 7.0.0; fixed in 7.0.10
- Microsoft.AspNetCore.App.Runtime.win-x86 (NuGet): affected from 6.0.0; fixed in 6.0.21

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-38180/ (Markdown: https://insights.sbomify.com/CVE-2023-38180/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-38180
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-38180
- OSV: https://osv.dev/vulnerability/CVE-2023-38180

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-38180/
Summaries are generated and may contain mistakes; the official description above is the record.
