CVE-2020-1108 evidence review
Microsoft .NET 5.0, .NET Core 2.1, .NET Core 3.1
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.
This record remains available for product and version identification, but it is not presented as a complete remediation procedure. Confirm the affected range and the supported fix in a direct vendor advisory before changing production systems.
Identify the product and installed version
Record whether Microsoft .NET 5.0, .NET Core 2.1, .NET Core 3.1 is present, where it is installed, and which interfaces are exposed.
- Record the product name, package or appliance identifier, and installed version.
- Identify internet-facing, administrative, API, and internal access paths.
- Preserve the pre-change configuration and relevant service logs.
Compare the affected range
Use the current record as an identification aid: >= 5.0.0 < publication, >= 2.1 < publication, >= 3.1 < publication, >= 2.0.0 < publication, >= 3.0.0 < publication, >= 3.5.0 < publication, >= 3.0.0.0 < publication, >= 3.0 < publication, >= 4.7.0 < publication, >= 4.8.0 < publication, >= 4.0.0.0 < publication, >= 15.9.0 < publication, >= 16.0 < publication, >= 7.0.0 < publication, >= 6.0 < publication, 5.0, >= 2.1 <= 2.1.18, >= 3.0 <= 3.1.4, 2.0, 3.0. Resolve incomplete inventory results before deciding that an asset is unaffected.
Verify the authoritative remediation source
Open the linked source material and locate a direct vendor advisory for this CVE. Confirm the supported fixed release and product-specific update path before making a production change.
Operational boundary
This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.