CVE-2023-36799: CWE-400: Uncontrolled Resource Consumption in Microsoft .NET 6.0
.NET Core and Visual Studio Denial of Service Vulnerability
AI Analysis
Technical 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.
Potential 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.
Mitigation Recommendations
1. Monitor official Microsoft channels for patches addressing CVE-2023-36799 and apply updates promptly once available. 2. Implement resource usage monitoring and alerting on .NET 6.0 applications to detect abnormal consumption patterns indicative of exploitation attempts. 3. Employ rate limiting, throttling, or request filtering at the application or network level to mitigate the impact of excessive resource consumption. 4. Use Web Application Firewalls (WAFs) or API gateways to block or challenge suspicious traffic that could trigger the vulnerability. 5. Conduct thorough testing of .NET 6.0 applications to identify and remediate any input handling or processing logic that could exacerbate resource consumption. 6. Consider deploying applications in containerized or isolated environments with resource quotas to limit the impact of potential DoS attacks. 7. Educate developers and system administrators about the vulnerability and encourage secure coding and resource management practices. 8. Review and harden user interaction points that could be exploited to trigger the vulnerability, such as input validation and request parsing.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Italy, Spain
CVE-2023-36799: CWE-400: Uncontrolled Resource Consumption in Microsoft .NET 6.0
Description
.NET Core and Visual Studio Denial of Service Vulnerability
AI-Powered Analysis
Technical Analysis
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.
Potential 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.
Mitigation Recommendations
1. Monitor official Microsoft channels for patches addressing CVE-2023-36799 and apply updates promptly once available. 2. Implement resource usage monitoring and alerting on .NET 6.0 applications to detect abnormal consumption patterns indicative of exploitation attempts. 3. Employ rate limiting, throttling, or request filtering at the application or network level to mitigate the impact of excessive resource consumption. 4. Use Web Application Firewalls (WAFs) or API gateways to block or challenge suspicious traffic that could trigger the vulnerability. 5. Conduct thorough testing of .NET 6.0 applications to identify and remediate any input handling or processing logic that could exacerbate resource consumption. 6. Consider deploying applications in containerized or isolated environments with resource quotas to limit the impact of potential DoS attacks. 7. Educate developers and system administrators about the vulnerability and encourage secure coding and resource management practices. 8. Review and harden user interaction points that could be exploited to trigger the vulnerability, such as input validation and request parsing.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- microsoft
- Date Reserved
- 2023-06-27T15:11:59.874Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6903adc7aebfcd54748fc7f9
Added to database: 10/30/2025, 6:26:15 PM
Last enriched: 10/30/2025, 7:00:11 PM
Last updated: 11/6/2025, 2:14:32 PM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2024-5651: Improper Control of Generation of Code ('Code Injection')
HighCVE-2024-57520: n/a
CriticalNevada Ransomware Attack Started Months Before It Was Discovered, Per Report
MediumAutomotive IT Firm Hyundai AutoEver Discloses Data Breach
MediumState-Sponsored Hackers Stole SonicWall Cloud Backups in Recent Attack
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.