A denial of service vulnerability exists when .NET Framework or .NET Core improperly handle web requests, aka '.Net Framework and .Net Core
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.9% (FIRST EPSS); higher than 92.1% of all records.
- 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.
- Fixed version: System.Private.Uri (NuGet) 4.3.2; dotnet (Red Hat:enterprise_linux:8::appstream) 0:2.1.507-2.el8_0; dotnet-debuginfo (Red Hat:enterprise_linux:8::appstream) 0:2.1.507-2.el8_0.
Low priority for now. Upgrade to System.Private.Uri (NuGet) 4.3.2; dotnet (Red Hat:enterprise_linux:8::appstream) 0:2.1.507-2.el8_0; dotnet-debuginfo (Red Hat:enterprise_linux:8::appstream) 0:2.1.507-2.el8_0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A denial of service vulnerability exists when .NET Framework or .NET Core improperly handle web requests, aka '.Net Framework and .Net Core Denial of Service Vulnerability'. This CVE ID is unique from CVE-2019-0820, CVE-2019-0981.
- Published
- May 16, 2019
- Updated
- Jun 16, 2026
- EPSS
- 4.9% · 92th percentile
- CWE
- CWE-19
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 · 4.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | .net core | cpe:2.3:a:microsoft:.net_core |
| microsoft | .net framework | cpe:2.3:a:microsoft:.net_framework |
| microsoft | windows server 2008 | cpe:2.3:o:microsoft:windows_server_2008 |
| microsoft | windows 10 | cpe:2.3:o:microsoft:windows_10 |
| microsoft | windows 8.1 | cpe:2.3:o:microsoft:windows_8.1 |
| microsoft | windows server 2012 | cpe:2.3:o:microsoft:windows_server_2012 |
| microsoft | windows server 2016 | cpe:2.3:o:microsoft:windows_server_2016 |
| microsoft | windows server 2019 | cpe:2.3:o:microsoft:windows_server_2019 |
| microsoft | windows 7 | cpe:2.3:o:microsoft:windows_7 |
| microsoft | windows rt 8.1 | cpe:2.3:o:microsoft:windows_rt_8.1 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft .net core1.0
- microsoft .net core1.1
- microsoft .net core2.1
- microsoft .net core2.2
- microsoft .net framework2.0
- microsoft .net framework3.0
- microsoft .net framework3.5
- microsoft .net framework3.5.1
- microsoft .net framework4.5.2
- microsoft .net framework4.6
- microsoft .net framework4.6.1
- microsoft .net framework4.6.2
- microsoft .net framework4.7
- microsoft .net framework4.7.1
- microsoft .net framework4.7.2
- microsoft .net framework4.8
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 Core
- 1, 1.1, 2.1, 2.2affected
Microsoft Microsoft .NET Framework 2.0
- Service Pack 2 on Windows Server 2008 for Itanium-Based Systems Service Pack 2, Service Pack 2 on Windows Server 2008 for 32-bit Systems Service Pack 2, Service Pack 2 on Windows Server 2008 for x64-based Systems Service Pack 2affected
Microsoft Microsoft .NET Framework 3.0
- Service Pack 2 on Windows Server 2008 for Itanium-Based Systems Service Pack 2, Service Pack 2 on Windows Server 2008 for 32-bit Systems Service Pack 2, Service Pack 2 on Windows Server 2008 for x64-based Systems Service Pack 2affected
Microsoft Microsoft .NET Framework 3.5
- Windows Server 2012, Windows Server 2012 (Server Core installation), Windows 8.1 for 32-bit systems, Windows 8.1 for x64-based systems, Windows Server 2012 R2, Windows Server 2012 R2 (Server Core installation), Windows 10 for 32-bit Systems, Windows 10 for x64-based Systems, Windows Server 2016, Windows 10 Version 1607 for 32-bit Systems, Windows 10 Version 1607 for x64-based Systems, Windows Server 2016 (Server Core installation) … (+13)affected
Microsoft Microsoft .NET Framework 3.5 on Windows 10 Version 1903 for 32-bit Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 on Windows 10 Version 1903 for x64-based Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 on Windows Server, version 1903 (Server Core installation)
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5.1
- Windows 7 for 32-bit Systems Service Pack 1, Windows 7 for x64-based Systems Service Pack 1, Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation), Windows Server 2008 R2 for Itanium-Based Systems Service Pack 1, Windows Server 2008 R2 for x64-based Systems Service Pack 1affected
Microsoft Microsoft .NET Framework 4.5.2
- Windows 7 for 32-bit Systems Service Pack 1, Windows 7 for x64-based Systems Service Pack 1, Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation), Windows Server 2008 R2 for x64-based Systems Service Pack 1, Windows Server 2012, Windows Server 2012 (Server Core installation), Windows 8.1 for 32-bit systems, Windows 8.1 for x64-based systems, Windows Server 2012 R2, Windows RT 8.1, Windows Server 2012 R2 (Server Core installation), Windows Server 2008 for 32-bit Systems Service Pack 2 … (+1)affected
Microsoft Microsoft .NET Framework 4.6
- Windows Server 2008 for 32-bit Systems Service Pack 2, Windows Server 2008 for x64-based Systems Service Pack 2affected
Microsoft Microsoft .NET Framework 4.6.2 on Windows 10 for 32-bit Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 4.6.2 on Windows 10 for x64-based Systems
- unspecifiedaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| NuGet | System.Private.Uri | from 4.3.0 · before 4.3.2 | 4.3.2 |
| Red Hat:enterprise_linux:8::appstream | dotnet | before 0:2.1.507-2.el8_0 | 0:2.1.507-2.el8_0 |
| Red Hat:enterprise_linux:8::appstream | dotnet-debuginfo | before 0:2.1.507-2.el8_0 | 0:2.1.507-2.el8_0 |
| Red Hat:enterprise_linux:8::appstream | dotnet-debugsource | before 0:2.1.507-2.el8_0 | 0:2.1.507-2.el8_0 |
| Red Hat:enterprise_linux:8::appstream | dotnet-host | before 0:2.1.11-2.el8_0 | 0:2.1.11-2.el8_0 |
| Red Hat:enterprise_linux:8::appstream | dotnet-host-debuginfo | before 0:2.1.11-2.el8_0 | 0:2.1.11-2.el8_0 |
| Red Hat:enterprise_linux:8::appstream | dotnet-host-fxr-2.1 | before 0:2.1.11-2.el8_0 | 0:2.1.11-2.el8_0 |
| Red Hat:enterprise_linux:8::appstream | dotnet-host-fxr-2.1-debuginfo | before 0:2.1.11-2.el8_0 | 0:2.1.11-2.el8_0 |
| Red Hat:enterprise_linux:8::appstream | dotnet-runtime-2.1 | before 0:2.1.11-2.el8_0 | 0:2.1.11-2.el8_0 |
| Red Hat:enterprise_linux:8::appstream | dotnet-runtime-2.1-debuginfo | before 0:2.1.11-2.el8_0 | 0:2.1.11-2.el8_0 |
| Red Hat:enterprise_linux:8::appstream | dotnet-sdk-2.1 | before 0:2.1.507-2.el8_0 | 0:2.1.507-2.el8_0 |
| Red Hat:enterprise_linux:8::appstream | dotnet-sdk-2.1.5xx | before 0:2.1.507-2.el8_0 | 0:2.1.507-2.el8_0 |
| Red Hat:enterprise_linux:8::appstream | dotnet-sdk-2.1.5xx-debuginfo | before 0:2.1.507-2.el8_0 | 0:2.1.507-2.el8_0 |
| Red Hat:rhel_dotnet:1.0::el7 | rh-dotnetcore10-dotnetcore | before 0:1.0.16-1.el7 | 0:1.0.16-1.el7 |
| Red Hat:rhel_dotnet:1.0::el7 | rh-dotnetcore10-dotnetcore-debuginfo | before 0:1.0.16-1.el7 | 0:1.0.16-1.el7 |
| Red Hat:rhel_dotnet:1.1::el7 | rh-dotnetcore11-dotnetcore | before 0:1.1.13-1.el7 | 0:1.1.13-1.el7 |
| Red Hat:rhel_dotnet:1.1::el7 | rh-dotnetcore11-dotnetcore-debuginfo | before 0:1.1.13-1.el7 | 0:1.1.13-1.el7 |
| Red Hat:rhel_dotnet:2.1::el7 | rh-dotnet21 | before 0:2.1-10.el7 | 0:2.1-10.el7 |
| Red Hat:rhel_dotnet:2.1::el7 | rh-dotnet21-dotnet | before 0:2.1.507-2.el7 | 0:2.1.507-2.el7 |
| Red Hat:rhel_dotnet:2.1::el7 | rh-dotnet21-dotnet-debuginfo | before 0:2.1.507-2.el7 | 0:2.1.507-2.el7 |
| Red Hat:rhel_dotnet:2.1::el7 | rh-dotnet21-dotnet-host | before 0:2.1.11-2.el7 | 0:2.1.11-2.el7 |
| Red Hat:rhel_dotnet:2.1::el7 | rh-dotnet21-dotnet-runtime-2.1 | before 0:2.1.11-2.el7 | 0:2.1.11-2.el7 |
| Red Hat:rhel_dotnet:2.1::el7 | rh-dotnet21-dotnet-sdk-2.1 | before 0:2.1.507-2.el7 | 0:2.1.507-2.el7 |
| Red Hat:rhel_dotnet:2.1::el7 | rh-dotnet21-dotnet-sdk-2.1.5xx | before 0:2.1.507-2.el7 | 0:2.1.507-2.el7 |
+14
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-1147A remote code execution vulnerability exists in .NET Framework, Microsoft SharePoint, and Visual Studio when the software fails to check theKEV89Now
- CVE-2018-0764Microsoft .NET Framework 1.1, 2.0, 3.0, 3.5, 3.5.1, 4, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 5.7 and .NET Core 1.0.33Monitor
- CVE-2019-1301A denial of service vulnerability exists when .NET Core improperly handles web requests, aka '.NET Core Denial of Service Vulnerability'.32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2019-0657Mar 5, 2019 · A vulnerability exists in certain .Net Framework API's and Visual Studio in the way they parse URL's, aka '.NET Framework and Visual Studio 24Monitor
- ← EarlierCVE-2019-0820May 16, 2019 · A denial of service vulnerability exists when .NET Framework and .NET Core improperly process RegEx strings, aka '.NET Framework and .NET Co32Monitor
- Later →CVE-2019-0981May 16, 2019 · A denial of service vulnerability exists when .NET Framework or .NET Core improperly handle web requests, aka '.Net Framework and .Net Core 31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| NuGet:System.Private.Uri | 4.3.2 | Package registry (OSV) |
| red hat:rh-dotnet21 | 0:2.1-10.el7 · Red Hat:rhel_dotnet:2.1::el7 | Package registry (OSV) |
| red hat:rh-dotnet21-dotnet | 0:2.1.507-2.el7 · Red Hat:rhel_dotnet:2.1::el7 | Package registry (OSV) |
| red hat:rh-dotnet21-dotnet-debuginfo | 0:2.1.507-2.el7 · Red Hat:rhel_dotnet:2.1::el7 | Package registry (OSV) |
| red hat:rh-dotnet21-dotnet-host | 0:2.1.11-2.el7 · Red Hat:rhel_dotnet:2.1::el7 | Package registry (OSV) |
| red hat:rh-dotnet21-dotnet-runtime-2.1 | 0:2.1.11-2.el7 · Red Hat:rhel_dotnet:2.1::el7 | Package registry (OSV) |
| red hat:rh-dotnet21-dotnet-sdk-2.1 | 0:2.1.507-2.el7 · Red Hat:rhel_dotnet:2.1::el7 | Package registry (OSV) |
| red hat:rh-dotnet21-dotnet-sdk-2.1.5xx | 0:2.1.507-2.el7 · Red Hat:rhel_dotnet:2.1::el7 | Package registry (OSV) |
| red hat:rh-dotnet21-runtime | 0:2.1-10.el7 · Red Hat:rhel_dotnet:2.1::el7 | Package registry (OSV) |
| red hat:rh-dotnetcore10-dotnetcore | 0:1.0.16-1.el7 · Red Hat:rhel_dotnet:1.0::el7 | Package registry (OSV) |
| red hat:rh-dotnetcore10-dotnetcore-debuginfo | 0:1.0.16-1.el7 · Red Hat:rhel_dotnet:1.0::el7 | Package registry (OSV) |
| red hat:rh-dotnetcore11-dotnetcore | 0:1.1.13-1.el7 · Red Hat:rhel_dotnet:1.1::el7 | Package registry (OSV) |
| red hat:rh-dotnetcore11-dotnetcore-debuginfo | 0:1.1.13-1.el7 · Red Hat:rhel_dotnet:1.1::el7 | Package registry (OSV) |
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-19 · Data Processing ErrorsCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.