CVE-2018-8171: Security feature bypass vulnerability exists in ASP.NET when the number of incorrect login attempts is not validated
7.5
CVSS Score
3.0
Basic Information
CVE ID
GHSA ID
EPSS Score
0.93267%
CWE
Published
10/16/2018
Updated
2/1/2023
KEV Status
No
Technology
C#
C#Technical Details
CVSS Vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| Microsoft.AspNetCore.Identity | nuget | >= 1.0.0, <= 1.0.5 | 1.0.6 |
| Microsoft.AspNetCore.Identity | nuget | >= 1.1.0, <= 1.1.5 | 1.1.6 |
| Microsoft.AspNetCore.Identity | nuget | >= 2.0.0, <= 2.0.3 | 2.0.4 |
| Microsoft.AspNetCore.Identity | nuget | >= 2.1.0, <= 2.1.1 | 2.1.2 |
Vulnerability Intelligence
Miggo AI
Miggo AIRoot Cause Analysis
The vulnerability centers on improper tracking of failed login attempts. In ASP.NET Identity:
- UserManager.CheckPasswordAsync is the core method for password validation that would need to track failed attempts
- SignInManager.PasswordSignInAsync is the main entry point for login attempts that should enforce lockout policies These functions would appear in stack traces during authentication attempts and were likely modified in patched versions to add proper attempt counting and lockout validation. The high confidence comes from their central role in authentication flows and the vulnerability's focus on attempt validation missing in security controls.