Skip to content

GHSA-32q7-gv7f-4cg5

Duplicate Advisory: Microsoft Security Advisory CVE-2024-21386: .NET Denial of Service Vulnerability

High Withdrawn Feb 13, 2024 NuGet
Severity
7.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
—
No score published
Known exploited
No
Not in CISA's catalog
Weakness
CWE-400 Uncontrolled Resource Consumption
Fix
6.0.27
Upgrade Microsoft.AspNetCore.App.Runtime.linux-arm to this version or later

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-g74q-5xw3-j7q9. This link is maintained to preserve external references.

Original Description

.NET Denial of Service Vulnerability

Affected versions

NuGet

PackageVulnerableFixed in
Microsoft.AspNetCore.App.Runtime.linux-arm
< 6.0.27
6.0.27

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

Microsoft.AspNetCore.App.Runtime.linux-arm NuGet → 6.0.27

dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-arm --version 6.0.27

Severity breakdown

CVSS 3.1 7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Weakness

CWE-400: Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource.

How to prevent it
  • Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
  • Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
  • Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
  • Implementation: Ensure that all failures in resource allocation place the system into a safe posture.

References

Timeline

  1. Published
  2. Withdrawn
  3. Last updated by the source
AdvisorySeverityWhy it's related
GHSA-f4g7-52wc-p8x7
Microsoft Security Advisory CVE-2026-96236 - ASP.NET Core Denial of Service Vulnerability
High Also affects Microsoft.AspNetCore.App.Runtime.linux-arm
GHSA-rv87-ccxw-8ggf
Microsoft Security Advisory CVE-2026-88092 - ASP.NET Core Security Feature Bypass Vulnerability
Critical Also affects Microsoft.AspNetCore.App.Runtime.linux-arm
GHSA-57xr-hfxx-jw5x
Microsoft Security Advisory CVE-2026-70196 - ASP.NET Core Denial of Service Vulnerability
Medium Also affects Microsoft.AspNetCore.App.Runtime.linux-arm
GHSA-fpq8-4vhr-rcxx
Microsoft Security Advisory CVE-2026-70188 - ASP.NET Core Security Feature Bypass Vulnerability
Critical Also affects Microsoft.AspNetCore.App.Runtime.linux-arm
GHSA-mf4x-w4gh-4656
Microsoft Security Advisory CVE-2026-70186 - ASP.NET Core Denial of Service Vulnerability
High Also affects Microsoft.AspNetCore.App.Runtime.linux-arm
GHSA-494h-xx7x-5frh
Microsoft Security Advisory CVE-2026-70183 - ASP.NET Core Security Feature Bypass Vulnerability
High Also affects Microsoft.AspNetCore.App.Runtime.linux-arm
GHSA-w5qq-qrpp-rf4c
Microsoft Security Advisory CVE-2026-70181 - ASP.NET Core Denial of Service Vulnerability
High Also affects Microsoft.AspNetCore.App.Runtime.linux-arm
GHSA-x3vp-85cm-q97r
Microsoft Security Advisory CVE-2026-70175 - ASP.NET Core Elevation of Privilege Vulnerability
High Also affects Microsoft.AspNetCore.App.Runtime.linux-arm
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor