Skip to main content
No exploitation reportedFix available

CVE-2020-1108

No exploitation reported by the sources we read.

  • Published2020-05-21

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A denial of service vulnerability exists when .NET Core or .NET Framework improperly handles web requests. An attacker who successfully exploited this vulnerability could cause a denial of service against a .NET Core or .NET Framework web application. The vulnerability can be exploited remotely, without authentication. A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the .NET Core or .NET Framework application. The update addresses the vulnerability by correcting how the .NET Core or .NET Framework web application handles web requests.

Timeline

dates in UTC
  1. 2020-05-2123:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-1108?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-1108?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Microsoft .net frameworkversion to verify
BranchAffectedFixed in
2.0= 2.0no fix published
3.0= 3.0no fix published
4.6= 4.6no fix published
3.5= 3.5no fix published
4.5= 4.5.2no fix published
4.6= 4.6.1no fix published
4.6= 4.6.2no fix published
4.7= 4.7no fix published
4.7= 4.7.1no fix published
4.7= 4.7.2no fix published
4.8= 4.8no fix published
3.5= 3.5.1no fix published
Microsoft .net core
BranchAffectedFixed in
2.1≥ 2.1, ≤ 2.1.18no fix published
3.x≥ 3.0, ≤ 3.1.4no fix published
2.1= 2.1no fix published
3.1= 3.1no fix published
Microsoft visual studio 2019
BranchAffectedFixed in
16.0= 16.0no fix published
16.4= 16.4no fix published
16.5= 16.5no fix published

19 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.17.5read 2026-10-23
  • NVDCVSS 2.05read 2026-10-23
  • FIRST EPSSEPSS score6.5 %2026-10-23
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2020-05-21
Last Modified
2026-08-19
NVD status
Modified

Frequently asked questions

What is CVE-2020-1108?

A denial of service vulnerability exists when .NET Core or .NET Framework improperly handles web requests. An attacker who successfully exploited this vulnerability could cause a denial of service against a .NET Core or .NET Framework web application. The vulnerability can be exploited remotely, without authentication. A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the .NET Core or .NET Framework application. The update addresses the vulnerability by correcting how the .NET Core or .NET Framework web application handles web requests.

Is CVE-2020-1108 actively exploited?

Active exploitation of CVE-2020-1108 has not been confirmed. Its EPSS score was 6.5% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-1108?

CVE-2020-1108 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month