Microsoft Corporation
ASP.NET
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at asp.net, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2018-8171 | 11 Jul 2018 | Web Pages 3.2.3 on Microsoft Visual Studio 2013 Update 5; Web Pages 3.2.3 on Microsoft Visual Studio 2015 Update 3; 1.0; 1.1; 2.0; Microsoft Visual Studio 2013 Update 5; Microsoft Visual Studio 2015 Update 3 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-11883 | 15 Nov 2017 | ASP.NET Core 1.0, ASP.NET Core 1.1, ASP.NET Core 2.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.