LiveActive security incident?Get immediate response
CVE Record

CVE-2024-21386: .NET Denial of Service Vulnerability

.NET Denial of Service Vulnerability

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability can let an unauthenticated remote attacker exhaust resources in affected .NET environments, disrupting applications or services. The supplied CVSS score is 7.5 because availability may be severely affected, while confidentiality and data integrity are not expected to be compromised.

Executive priority

Treat this as a high-priority availability risk. Remediate exposed or business-critical services promptly, while recognizing that the supplied evidence does not show data theft, integrity loss, or confirmed active exploitation.

Technical view

CVE-2024-21386 is a CWE-400 resource-consumption denial-of-service flaw affecting listed ASP.NET Core 6.0, 7.0, and 8.0 releases and listed Visual Studio 2022 versions. Its CVSS vector indicates network reachability, low attack complexity, no privileges, no user interaction, and high availability impact.

Likely exposure

Prioritize systems running the listed ASP.NET Core releases, especially network-accessible applications. The bundle also identifies Visual Studio 2022 versions 17.4, 17.6, and 17.8, but does not explain the conditions under which those installations are exposed.

Exploitation context

The supplied temporal vector reports proof-of-concept exploit maturity. However, the CVE is not listed as KEV, and the source bundle provides no evidence of active exploitation. Treat exploitation status as unconfirmed rather than assuming attacks are occurring.

Researcher notes

The available description does not identify the vulnerable component, triggering input, resource type, fixed build numbers, or affected configuration prerequisites. The affected-version entries are broad. Consult the Microsoft advisory and CVE record for precise applicability; avoid inferring that every application on a listed major release is exploitable.

Mitigation direction

  • Review Microsoft's CVE advisory for applicable security updates and deployment guidance.
  • Update affected ASP.NET Core and Visual Studio installations according to Microsoft's supported instructions.
  • Prioritize externally reachable and business-critical .NET services.
  • Monitor resource exhaustion, service instability, and unusual request spikes until remediation is verified.

Validation and detection

  • Inventory deployed ASP.NET Core runtimes, SDKs, applications, and listed Visual Studio versions.
  • Compare installed versions and update status with Microsoft's CVE advisory.
  • Confirm security updates are present across production, staging, build, and developer systems.
  • Use non-destructive availability monitoring to verify services remain stable after remediation.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-21386 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C3.93.6microsoft

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2024-21386Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftASP.NET Core 6.06.0Listed
MicrosoftASP.NET Core 7.07.0.0Listed
MicrosoftASP.NET Core 8.08.0Listed
MicrosoftMicrosoft Visual Studio 2022 version 17.417.4.0Listed
MicrosoftMicrosoft Visual Studio 2022 version 17.617.6.0Listed
MicrosoftMicrosoft Visual Studio 2022 version 17.817.8.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.