Microsoft security update for CVE-2018-8171 — ASP.NET
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2018-8171. This page also shows what EchelonGraph holds for CVE-2018-8171, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products7
- ASP.NET Core 1.0
- ASP.NET Core 1.1
- ASP.NET Core 2.0
- ASP.NET MVC 5.2 on Microsoft Visual Studio 2013 Update 5
- ASP.NET MVC 5.2 on Microsoft Visual Studio 2015 Update 3
- ASP.NET Web Pages 3.2.3 on Microsoft Visual Studio 2013 Update 5
- ASP.NET Web Pages 3.2.3 on Microsoft Visual Studio 2015 Update 3
✅ Updates Microsoft lists: 2 updates
2 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | — |
| — | Security Update | — |
🧭 EchelonGraph on CVE-2018-8171
- EchelonGraph score
- 7.5 HIGH
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
A Security Feature Bypass vulnerability exists in ASP.NET when the number of incorrect login attempts is not validated, aka "ASP.NET Security Feature Bypass Vulnerability." This affects ASP.NET, ASP.NET Core 1.1, ASP.NET Core 1.0, ASP.NET Core 2.0, ASP.NET MVC 5.2.
Published by Microsoft Corporation, the CVE Numbering Authority that assigned CVE-2018-8171, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).