Skip to content

GHSA-25c8-p796-jg6r BIT-dotnet-2023-33170 BIT-dotnet-sdk-2023-33170 CVE-2023-33170

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

High NuGet
Severity
8.1 / 10
High · CVSS 3.1
Exploit chance (EPSS)
1.99%
Chance of exploitation in the next 30 days. Higher than 80.70% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Fix
Available
14 packages have a fixed version

Description

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 uses the following package versions, ensure you update to the latest version of .NET.

ASP.NET Core 2.1
Package name Affected version Patched version
Microsoft.AspNetCore.Identity <=2.1.39 2.1.39
Microsoft.AspNet.Identity.Owin
Package name Affected version Patched version
Microsoft.AspNet.Identity.Owin <= 2.2.3 2.2.4
ASP.NET 6.0
Package name Affected version Patched version

Microsoft.AspNetCore.App.Runtime.linux-arm | <= 6.0.19 | 6.0.20 Microsoft.AspNetCore.App.Runtime.linux-arm64 | <= 6.0.19 | 6.0.20 Microsoft.AspNetCore.App.Runtime.linux-musl-arm | <= 6.0.19 | 6.0.20 Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 | <= 6.0.19 | 6.0.20 Microsoft.AspNetCore.App.Runtime.linux-musl-x64 | <= 6.0.19 | 6.0.20 Microsoft.AspNetCore.App.Runtime.linux-x64 | <= 6.0.19 | 6.0.20 Microsoft.AspNetCore.App.Runtime.osx-arm64 | <= 6.0.19 | 6.0.20 Microsoft.AspNetCore.App.Runtime.osx-x64 | <= 6.0.19 | 6.0.20 Microsoft.AspNetCore.App.Runtime.win-arm | <= 6.0.19 | 6.0.20 Microsoft.AspNetCore.App.Runtime.win-arm64 | <= 6.0.19 | 6.0.20 Microsoft.AspNetCore.App.Runtime.win-x64 | <= 6.0.19 | 6.0.20 Microsoft.AspNetCore.App.Runtime.win-x86 | <= 6.0.19 | 6.0.20

ASP.NET 7.0
Package name Affected version Patched version
Microsoft.AspNetCore.App.Runtime.linux-arm <= 7.0.9 7.0.9
Microsoft.AspNetCore.App.Runtime.linux-arm64 <= 7.0.9 7.0.9
Microsoft.AspNetCore.App.Runtime.linux-musl-arm <= 7.0.9 7.0.9
Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 <= 7.0.9 7.0.9
Microsoft.AspNetCore.App.Runtime.linux-musl-x64 <= 7.0.9 7.0.9
Microsoft.AspNetCore.App.Runtime.linux-x64 <= 7.0.9 7.0.9
Microsoft.AspNetCore.App.Runtime.osx-arm64 <= 7.0.9 7.0.9
Microsoft.AspNetCore.App.Runtime.osx-x64 <= 7.0.9 7.0.9
Microsoft.AspNetCore.App.Runtime.win-arm <= 7.0.9 7.0.9
Microsoft.AspNetCore.App.Runtime.win-arm64 <= 7.0.9 7.0.9
Microsoft.AspNetCore.App.Runtime.win-x64 <= 7.0.9 7.0.9
Microsoft.AspNetCore.App.Runtime.win-x86 <= 7.0.9 7.0.9

Advisory FAQ

How do I know if I am affected?

If you have a runtime or SDK with a version listed, or an affected package listed in affected software, you're exposed to the vulnerability.

How do I fix the issue?
  • To fix the issue please install the latest version of .NET 6.0 or .NET 7.0. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs.
  • If you are using one of the affected packages, please update to the patched version listed above.
  • If you have .NET 6.0 or greater installed, you can list the versions you have installed by running the dotnet --info command. You will see output like the following;
.NET Core SDK (reflecting any global.json):

 Version:   6.0.300
 Commit:    8473146e7d

Runtime Environment:

 OS Name:     Windows
 OS Version:  10.0.18363
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\6.0.300\

Host (useful for support):

  Version: 6.0.5
  Commit:  8473146e7d

.NET Core SDKs installed:

  6.0.300 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:

  Microsoft.AspNetCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

.NET 6.0 and and .NET 7.0 updates are also available from Microsoft Update. To access this either type "Check for updates" in your Windows search, or open Settings, choose Update & Security and then click Check for Updates.

Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.

Additionally, if you've deployed self-contained applications targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.

Other Information

Reporting Security Issues

If you have found a potential security issue in .NET 6.0 or .NET 7.0, please email details to secure@microsoft.com. Reports may qualify for the Microsoft .NET Core & .NET 5 Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.

Support

You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime and https://github.com/dotnet/aspnet/. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.

Disclaimer

The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

External Links

CVE-2023-33170

Revisions

V1.0 (July 11, 2023): Advisory published.

Version 1.0

Last Updated 2023-07-11

Affected versions

NuGet

PackageVulnerableFixed in
Microsoft.AspNet.Identity.Owin
< 2.2.4
2.2.4
Microsoft.AspNetCore.App.Runtime.linux-arm
< 6.0.20
6.0.20
Microsoft.AspNetCore.App.Runtime.linux-arm
>= 7.0.0, < 7.0.9
7.0.9
Microsoft.AspNetCore.App.Runtime.linux-arm64
< 6.0.20
6.0.20
Microsoft.AspNetCore.App.Runtime.linux-arm64
>= 7.0.0, < 7.0.9
7.0.9
Microsoft.AspNetCore.App.Runtime.linux-musl-arm
< 6.0.20
6.0.20
Microsoft.AspNetCore.App.Runtime.linux-musl-arm
>= 7.0.0, < 7.0.9
7.0.9
Microsoft.AspNetCore.App.Runtime.linux-musl-arm64
< 6.0.20
6.0.20
Microsoft.AspNetCore.App.Runtime.linux-musl-arm64
>= 7.0.0, < 7.0.9
7.0.9
Microsoft.AspNetCore.App.Runtime.linux-musl-x64
>= 7.0.0, < 7.0.9
7.0.9
Microsoft.AspNetCore.App.Runtime.linux-musl-x64
< 6.0.20
6.0.20
Microsoft.AspNetCore.App.Runtime.linux-x64
< 6.0.20
6.0.20
Microsoft.AspNetCore.App.Runtime.linux-x64
>= 7.0.0, < 7.0.9
7.0.9
Microsoft.AspNetCore.App.Runtime.osx-arm64
>= 7.0.0, < 7.0.9
7.0.9
Microsoft.AspNetCore.App.Runtime.osx-arm64
< 6.0.20
6.0.20
Microsoft.AspNetCore.App.Runtime.osx-x64
< 6.0.20
6.0.20
Microsoft.AspNetCore.App.Runtime.osx-x64
>= 7.0.0, < 7.0.9
7.0.9
Microsoft.AspNetCore.App.Runtime.win-arm
< 6.0.20
6.0.20
Microsoft.AspNetCore.App.Runtime.win-arm
>= 7.0.0, < 7.0.9
7.0.9
Microsoft.AspNetCore.App.Runtime.win-arm64
< 6.0.20
6.0.20
Microsoft.AspNetCore.App.Runtime.win-arm64
>= 7.0.0, < 7.0.9
7.0.9
Microsoft.AspNetCore.App.Runtime.win-x64
< 6.0.20
6.0.20
Microsoft.AspNetCore.App.Runtime.win-x64
>= 7.0.0, < 7.0.9
7.0.9
Microsoft.AspNetCore.App.Runtime.win-x86
< 6.0.20
6.0.20
Microsoft.AspNetCore.App.Runtime.win-x86
>= 7.0.0, < 7.0.9
7.0.9
Microsoft.AspNetCore.Identity
< 2.1.39
2.1.39

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

Microsoft.AspNet.Identity.Owin NuGet → 2.2.4

dotnet
dotnet add package Microsoft.AspNet.Identity.Owin --version 2.2.4

Microsoft.AspNetCore.App.Runtime.linux-arm NuGet → 6.0.20

dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-arm --version 6.0.20

Microsoft.AspNetCore.App.Runtime.linux-arm64 NuGet → 6.0.20

dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-arm64 --version 6.0.20

Microsoft.AspNetCore.App.Runtime.linux-musl-arm NuGet → 6.0.20

dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-musl-arm --version 6.0.20

Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 NuGet → 6.0.20

dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 --version 6.0.20

Microsoft.AspNetCore.App.Runtime.linux-musl-x64 NuGet → 7.0.9

dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-musl-x64 --version 7.0.9

Microsoft.AspNetCore.App.Runtime.linux-x64 NuGet → 6.0.20

dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-x64 --version 6.0.20

Microsoft.AspNetCore.App.Runtime.osx-arm64 NuGet → 7.0.9

dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.osx-arm64 --version 7.0.9

Microsoft.AspNetCore.App.Runtime.osx-x64 NuGet → 6.0.20

dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.osx-x64 --version 6.0.20

Microsoft.AspNetCore.App.Runtime.win-arm NuGet → 6.0.20

dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.win-arm --version 6.0.20

Microsoft.AspNetCore.App.Runtime.win-arm64 NuGet → 6.0.20

dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.win-arm64 --version 6.0.20

Microsoft.AspNetCore.App.Runtime.win-x64 NuGet → 6.0.20

dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.win-x64 --version 6.0.20

Microsoft.AspNetCore.App.Runtime.win-x86 NuGet → 6.0.20

dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.win-x86 --version 6.0.20

Microsoft.AspNetCore.Identity NuGet → 2.1.39

dotnet
dotnet add package Microsoft.AspNetCore.Identity --version 2.1.39

Severity breakdown

CVSS 3.1 8.1

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

How to prevent it
  • Architecture and Design: In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
  • Architecture and Design: Use thread-safe capabilities such as the data access abstraction in Spring.
  • Architecture and Design: Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring. Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).
  • Implementation: When using multithreading and operating on shared variables, only use thread-safe functions.
  • Implementation: Use atomic operations on shared variables. Be wary of innocent-looking constructs such as "x++". This may appear atomic at the code layer, but it is actually non-atomic at the instruction layer, since it involves a read, followed by a computation, followed by a write.
  • Implementation: Use a mutex if available, but be sure to avoid related weaknesses such as CWE-412.
  • Implementation: Avoid double-checked locking (CWE-609) and other implementation errors that arise when trying to avoid the overhead of synchronization.
  • Implementation: Disable interrupts or signals over critical parts of the code, but also make sure that the code does not go into a large or infinite loop.
  • Implementation: Use the volatile type modifier for critical variables to avoid unexpected compiler optimization or reordering. This does not necessarily solve the synchronization problem, but it can help.
  • Architecture and Design, Operation: Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-vmch-3w2x-vhgq
.NET Denial of Service Vulnerability
High Known exploited Also affects Microsoft.AspNetCore.App.Runtime.win-arm64
GHSA-f4g7-52wc-p8x7
Microsoft Security Advisory CVE-2026-96236 - ASP.NET Core Denial of Service Vulnerability
High Also affects Microsoft.AspNetCore.App.Runtime.linux-arm
GHSA-rv87-ccxw-8ggf
Microsoft Security Advisory CVE-2026-88092 - ASP.NET Core Security Feature Bypass Vulnerability
Critical Also affects Microsoft.AspNetCore.App.Runtime.linux-arm
GHSA-57xr-hfxx-jw5x
Microsoft Security Advisory CVE-2026-70196 - ASP.NET Core Denial of Service Vulnerability
Medium Also affects Microsoft.AspNetCore.App.Runtime.linux-arm
GHSA-fpq8-4vhr-rcxx
Microsoft Security Advisory CVE-2026-70188 - ASP.NET Core Security Feature Bypass Vulnerability
Critical Also affects Microsoft.AspNetCore.App.Runtime.linux-arm
GHSA-mf4x-w4gh-4656
Microsoft Security Advisory CVE-2026-70186 - ASP.NET Core Denial of Service Vulnerability
High Also affects Microsoft.AspNetCore.App.Runtime.linux-arm
GHSA-494h-xx7x-5frh
Microsoft Security Advisory CVE-2026-70183 - ASP.NET Core Security Feature Bypass Vulnerability
High Also affects Microsoft.AspNetCore.App.Runtime.linux-arm
GHSA-w5qq-qrpp-rf4c
Microsoft Security Advisory CVE-2026-70181 - ASP.NET Core Denial of Service Vulnerability
High Also affects Microsoft.AspNetCore.App.Runtime.linux-arm
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor