ASP.NET Core Denial of Service Vulnerability
- Published
- Nov 14, 2023
- Updated
- Jun 17, 2026
- EPSS
- 2.8% · 86th percentile
- CWE
- CWE-400
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.8%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · microsoft
- 8.2
- 0.7 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H/E:U/RL:O/RC:C
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| microsoft | visual studio 2022 | cpe:2.3:a:microsoft:visual_studio_2022 |
| microsoft | asp.net core | cpe:2.3:a:microsoft:asp.net_core |
| microsoft | .net | cpe:2.3:a:microsoft:.net |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft asp.net core8.0.0
- microsoft visual studio 202217.2 and later · before 17.2.22
- microsoft visual studio 202217.4 and later · before 17.4.14
- microsoft visual studio 202217.6 and later · before 17.6.10
- microsoft visual studio 202217.7 and later · before 17.7.7
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft .NET 8.0
- 8.0 and later · before 8.0.0affected
Microsoft ASP.NET Core 8.0
- 8.0 and later · before 8.0.0affected
Microsoft Microsoft Visual Studio 2022 version 17.2
- 17.2.0 and later · before 17.2.22affected
Microsoft Microsoft Visual Studio 2022 version 17.4
- 17.4.0 and later · before 17.4.14affected
Microsoft Microsoft Visual Studio 2022 version 17.6
- 17.6.0 and later · before 17.6.10affected
Microsoft Microsoft Visual Studio 2022 version 17.7
- 17.7.0 and later · before 17.7.7affected
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-36758Visual Studio Elevation of Privilege Vulnerability39Monitor
- CVE-2026-71328.NET and Visual Studio Remote Code Execution Vulnerability35Monitor
- CVE-2026-21256GitHub Copilot and Visual Studio Remote Code Execution Vulnerability35Monitor
- CVE-2024-38229.NET and Visual Studio Remote Code Execution Vulnerability33Monitor
- CVE-2026-21257GitHub Copilot and Visual Studio Elevation of Privilege Vulnerability32Monitor
- CVE-2025-53773GitHub Copilot and Visual Studio Remote Code Execution Vulnerability32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) { return node.children.map(expand);}Fixed
const MAX_DEPTH = 32;function expand(node, depth = 0) { if (depth > MAX_DEPTH) throw new Error("too deep"); return node.children.map((c) => expand(c, depth + 1));}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.