VulnerabilityPublished 12 Sep 2023Updated 30 Oct 2025

CVE-2023-36799: Microsoft .NET 6.0 · Uncontrolled Resource Consumption

Affects Microsoft .NET 6.0Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 4.6% chance of exploitation in 30 days – higher than 91% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Temporal metrics

Exploit Code Maturity: Unproven
Remediation Level: Official Fix
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Exploit Code Maturity: Unproven: No exploit code is available, or an exploit is theoretical.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Sep 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
NuGetmicrosoft.netcore.app`pkg:nuget/microsoft.netcore.app`Other threats	Affected =6.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Monitor official Microsoft channels for patches addressing CVE-2023-36799 and apply updates promptly once available.
Implement resource usage monitoring and alerting on .NET 6.0 applications to detect abnormal consumption patterns indicative of exploitation attempts.
Employ rate limiting, throttling, or request filtering at the application or network level to mitigate the impact of excessive resource consumption.
Use Web Application Firewalls (WAFs) or API gateways to block or challenge suspicious traffic that could trigger the vulnerability.
Conduct thorough testing of .NET 6.0 applications to identify and remediate any input handling or processing logic that could exacerbate resource consumption.
Consider deploying applications in containerized or isolated environments with resource quotas to limit the impact of potential DoS attacks.
Educate developers and system administrators about the vulnerability and encourage secure coding and resource management practices.
Review and harden user interaction points that could be exploited to trigger the vulnerability, such as input validation and request parsing.

Description

.NET Core and Visual Studio Denial of Service Vulnerability

Impact

For European organizations, the primary impact of CVE-2023-36799 is the potential for denial of service attacks that disrupt availability of applications and services built on .NET 6.0. This can lead to operational downtime, loss of productivity, and potential financial losses, especially for sectors relying heavily on digital services such as finance, healthcare, government, and e-commerce. Since the vulnerability does not affect confidentiality or integrity, data breaches or data manipulation risks are not a concern here. However, service outages can indirectly affect customer trust and regulatory compliance, particularly under regulations like the GDPR that emphasize service availability and resilience. Organizations running public-facing .NET 6.0 applications or internal critical systems are at risk of disruption if attackers exploit this vulnerability to exhaust system resources. The lack of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits once patches are released. European entities with high dependency on Microsoft technologies and cloud services leveraging .NET 6.0 should consider this vulnerability a significant availability risk.

Summary

CVE-2023-36799 is a denial of service (DoS) vulnerability identified in Microsoft .NET 6.0, specifically version 6.0.0. The vulnerability is classified under CWE-400, which pertains to uncontrolled resource consumption. This means that an attacker can craft requests or inputs that cause the .NET runtime or applications built on it to consume excessive system resources such as CPU, memory, or threads, eventually leading to service degradation or complete outage. The vulnerability can be exploited remotely over the network without requiring any privileges, although it does require user interaction, such as processing a specially crafted request or input. The CVSS v3.1 base score is 6.5, reflecting a medium severity level, with the vector indicating network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), user interaction required (UI:R), and impact limited to availability (A:H) with no confidentiality or integrity impact. There are no known exploits in the wild at the time of publication, and no official patches have been linked yet. The vulnerability affects .NET 6.0.0, a widely used framework for building modern applications and services, including web applications, APIs, and microservices. Uncontrolled resource consumption vulnerabilities can be particularly disruptive in environments where .NET applications serve critical business functions or high volumes of users, as they can cause denial of service conditions that degrade user experience or halt operations. Given the broad adoption of .NET 6.0 in enterprise environments, this vulnerability poses a tangible risk to availability if exploited.

CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
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.
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.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36799 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2025, 19:00 UTC

WeaknessesCWE-400

Technical details

References

Community reviews

Related threats