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

CVE-2022-38013 — Microsoft.AspNetCore.App.…

HIGH

CVE-2022-38013 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in Microsoft.AspNetCore.App.Runtime.linux-arm. A fix is available for Microsoft.AspNetCore.App.Runtime.linux-arm — see the affected versions and patch details below.

.NET Denial of Service Vulnerability

Also known asBIT-dotnet-2022-38013BIT-dotnet-sdk-2022-38013GHSA-r8m2-4x37-6592
Published
Sep 13, 2022
Updated
Jul 8, 2026
Affected
22 pkgs
Patched
22 / 22
Exploits
None indexed
Exploitation data as of Sep 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-38013.

EPSS Exploitation Probability

via FIRST.org ↗
4.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

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-2022-38013 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 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

22 pkgs affected
.NETMicrosoft.AspNetCore.App.Runtime.linux-arm.NETMicrosoft.AspNetCore.App.Runtime.linux-arm64.NETMicrosoft.AspNetCore.App.Runtime.linux-musl-arm64.NETMicrosoft.AspNetCore.App.Runtime.linux-musl-x64.NETMicrosoft.AspNetCore.App.Runtime.linux-x64.NETMicrosoft.AspNetCore.App.Runtime.osx-x64.NETMicrosoft.AspNetCore.App.Runtime.win-arm.NETMicrosoft.AspNetCore.App.Runtime.win-arm64+14 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

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core 3.1 and .NET 6.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

A denial of service vulnerability exists in ASP.NET Core 3.1 and .NET 6.0 where a malicious client could cause a stack overflow which may result in a denial of service attack when an attacker sends a customized payload that is parsed during model binding.

<a name="affected-software"></a>Affected software

  • Any .NET 6.0 application running on .NET 6.0.8 or earlier.
  • Any ASP.NET Core 3.1 application running on .NET Core 3.1.28 or earlier. If your application uses the following package versions, ensure you update to the latest version of .NET.

<a name="ASP.NET Core 3.1"></a>.NET Core 3.1

<a name=".NET 6"></a>.NET 6

Other

Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/234 An Issue for this can be found at https://github.com/dotnet/aspnetcore/issues/43953 MSRC details for this can be found at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-38013

Affected Packages

22 total 22 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.AspNetCore.App.Runtime.linux-arm≥ 3.1.0&&< 3.1.293.1.29dotnet add package Microsoft.AspNetCore.App.Runtime.linux-arm --version 3.1.29
.NETNuGetMicrosoft.AspNetCore.App.Runtime.linux-arm64≥ 3.1.0&&< 3.1.293.1.29dotnet add package Microsoft.AspNetCore.App.Runtime.linux-arm64 --version 3.1.29
.NETNuGetMicrosoft.AspNetCore.App.Runtime.linux-musl-arm64≥ 3.1.0&&< 3.1.293.1.29dotnet add package Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 --version 3.1.29
.NETNuGetMicrosoft.AspNetCore.App.Runtime.linux-musl-x64≥ 3.1.0&&< 3.1.293.1.29dotnet add package Microsoft.AspNetCore.App.Runtime.linux-musl-x64 --version 3.1.29
.NETNuGetMicrosoft.AspNetCore.App.Runtime.linux-x64≥ 3.1.0&&< 3.1.293.1.29dotnet add package Microsoft.AspNetCore.App.Runtime.linux-x64 --version 3.1.29
.NETNuGetMicrosoft.AspNetCore.App.Runtime.osx-x64≥ 3.1.0&&< 3.1.293.1.29dotnet add package Microsoft.AspNetCore.App.Runtime.osx-x64 --version 3.1.29

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.linux-arm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update Microsoft.AspNetCore.App.Runtime.linux-arm to 3.1.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-38013 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-38013 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2022-38013. 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.

Red HatModerate
ProductFixed inAdvisory
.NET Core on Red Hat Enterprise Linuxrh-dotnet31-dotnet-0:3.1.423-1.el7_9RHSA-2022:6522
.NET Core on Red Hat Enterprise Linuxrh-dotnet60-dotnet-0:6.0.109-1.el7_9RHSA-2022:6520
Red Hat Enterprise Linux 8dotnet3.1-0:3.1.423-1.el8_6RHSA-2022:6523
Red Hat Enterprise Linux 8dotnet6.0-0:6.0.109-1.el8_6RHSA-2022:6539
Red Hat Enterprise Linux 9dotnet6.0-0:6.0.109-1.el9_0RHSA-2022:6521

Frequently Asked Questions

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core 3.1 and .NET 6.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A denial of service vulnerability exists in ASP.NET Core 3.1 and .NET 6.0 where a malicious client could cause a stack overflow which may result in a denial of service attack when an attacker sends a customized payload that is parsed during model binding. ## <a name="affected-software"></a>Affected software * Any .NET 6.0 application running on .NET 6.
O3 Security · Impact-Aware SCA

Is CVE-2022-38013 in your dependencies?

O3 Security finds CVE-2022-38013 across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2022-38013: DoS (High 7.5) | O3 Security