CVE-2018-8171
Exploitation likely. EPSS gives it a 10% chance of exploitation in the next 30 days. A vendor fix is available.
What to do
The vendor has published a fix. Version details are below where the sources state them.
Steps
Written by AI from the record- Check whether any application uses ASP.NET Core 1.0, 1.1, or 2.0, or ASP.NET MVC 5.2, and whether it uses Microsoft.AspNetCore.Identity for sign-in.
- Update Microsoft.AspNetCore.Identity to 1.0.6 for the 1.0 branch, 1.1.6 for 1.1, 2.0.4 for 2.0, or 2.1.2 for 2.1.
- Test sign-in failures after updating to confirm repeated incorrect passwords trigger your intended account-lockout controls.
- Until updated, restrict public access to affected sign-in pages where practical and review accounts with unusually high failed-login activity.
What it is
From the CVE record
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.
In plain language
Written by AI from the recordIf you run ASP.NET Core 1.0, 1.1, or 2.0, or ASP.NET MVC 5.2, update it because login protections may not stop repeated password guesses.
Authentication bypass in ASP.NET identity handling caused by failure to validate and enforce the count of unsuccessful sign-in attempts.
If you're affected
- Account takeover risk
- Unauthorized account changes
- Fraudulent user actions
- Customer trust damage
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
10% chance of exploitation activity in the next 30 days, which ranks it in the 96th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
9 events over 2988 days, from the signal feeds we watch.
- EPSS band change0 → moderateepss band change
- OpenVAS check added
- EPSS band changemoderate → low
- Patch availablerecord updated
- Publishedweakness classified, att&ck mapped
Affected products
And 1 more affected product. See all after sign-in
Technical detail
CVSS 3.0 vector
Open in the CVSS calculatorCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Scored 7.5 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality NoneNo confidentiality impact
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability NoneNo availability impact
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
- securitytracker.com/id/1041267
- securityfocus.com/bid/104659
- portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8171
And 2 more references. See all after sign-in
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for ASP.NET, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI