Skip to content

← Public intelligence

NuGet package

microsoft.aspnetcore.identity

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.0NuGetPublished

    Microsoft Security Advisory CVE-2025-24070: .NET Elevation of Privilege Vulnerability

    CVE-2025-24070 · GHSA-2865-hh9g-w894

    Affected
    • NuGet microsoft.aspnetcore.identity >= 2.3.0, <= 2.3.0
    Fixed in
    2.3.1· Partial vendor fix
    Issue
    Microsoft Security Advisory CVE-2025-24070: .NET Elevation of Privilege Vulnerability Executive summary Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 9.0, ASP.NET Core 8.0, ASP.NET Core 6.0, and ASP.NET Core 2.3. This advisory also provides guidance on what developers can do to update their applications to address this vulnerability. A vulnerability exists in ASP.NET Core applications calling RefreshSignInAsync with an improperly authenticated user parameter that could allow an attacker to sign into another user's account, resulting in Elevation of Privilege. Announcement Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/348 Mitigation factors Microsoft has not identified any mitigating factors for this vulnerability. Affected software Any ASP.NET Core 9.0 application running on ASP.NET Core 9.0.2 or earlier. Any ASP.NET Core application running on ASP.NET Core 8.0.13 or earlier. Any…

    Recommended action: Upgrade to 2.3.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 8.1NuGetPublished

    Microsoft Security Advisory CVE-2023-33170: .NET Security Feature Bypass Vulnerability

    CVE-2023-33170 · GHSA-25c8-p796-jg6r

    Affected
    • NuGet microsoft.aspnetcore.identity < 2.1.39
    Fixed in
    2.1.39· Vendor fix available
    Issue
    Microsoft Security Advisory CVE-2023-33170: .NET Security Feature Bypass Vulnerability Executive summary Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 2.1 and above. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A vulnerability exist in ASP.NET Core applications where account lockout maximum failed attempts may not be immediately updated, allowing an attacker to try more passwords. Discussion Discussion for this issue can be found at https://github.com/dotnet/aspnetcore/issues/49334 Mitigation factors Microsoft has not identified any mitigating factors for this vulnerability. Affected software Any ASP.NET 7.0 application running on .NET 7.0.8 or earlier. Any ASP.NET 6.0 application running on .NET 6.0.19 or earlier. Any ASP.NET Core 2.1 application consuming the package Microsoft.AspNetCore.Identity version 2.1.31 or earlier. If your application…

    Recommended action: Upgrade to 2.1.39 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. High, CVSS 7.5NuGetPublished

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

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

    Affected
    • NuGet microsoft.aspnetcore.identity >= 1.0.0, <= 1.0.5; >= 1.1.0, <= 1.1.5; >= 2.0.0, <= 2.0.3; >= 2.1.0, <= 2.1.1
    Fixed in
    2.1.21.0.62.0.41.1.6· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 2.1.2, 2.0.4, 1.1.6 or 1.0.6 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →