CVE-2018-8171: Security feature bypass vulnerability exists in ASP.NET when the number of incorrect login attempts is not validated

CVE-2018-8171 · Severity: low · CVSS 3 · Published 2018-10-16

Security feature bypass vulnerability exists in ASP.NET when the number of incorrect login attempts is not validated

Technologies: Microsoft.AspNetCore.Identity (NuGet). Vendors: NuGet.

Quick answers

Is CVE-2018-8171 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2018-8171 being exploited in the wild.
How severe is CVE-2018-8171?
Low severity, with a CVSS score of 3, published 16 October 2018.
Which products and versions are affected?
Microsoft.AspNetCore.Identity (NuGet) ECOSYSTEM:introduced=1.0.0,fixed=1.0.6.
Is there a fix for CVE-2018-8171?
Yes. Microsoft.AspNetCore.Identity (NuGet): upgrade to 1.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-8171?
Check whether you run Microsoft.AspNetCore.Identity (NuGet) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Microsoft.AspNetCore.Identity (NuGet): upgrade to 1.0.6 or later
    dotnet add package Microsoft.AspNetCore.Identity --version 1.0.6

Affected products

  • Microsoft.AspNetCore.Identity (NuGet) ECOSYSTEM:introduced=1.0.0,fixed=1.0.6

Identifiers

  • CVE-2018-8171
  • GHSA-vhvh-528q-ff3p

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.