Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-3rq8-h3gj-r5c6
No affected components available
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 6.0, .NET 5.0 and .NET Core 3.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A vulnerability exists in .NET 6.0, .NET 5.0 and .NET core 3.1 where a malicious client can manipulate cookies and cause a Denial of Service.
Affected software
- Any .NET 6.0 application running on .NET 6.0.4 or earlier.
- Any .NET 5.0 application running .NET 5.0.16 or earlier.
- Any .NET Core 3.1 application running on .NET Core 3.1.24 or earlier.
Affected packages
.NET Core 3.1
| Package name | Affected versions | Patched versions | |---------------------------------------------------|-------------------|------------------| | Microsoft.Owin.Security.Cookies | <4.2.2 | 4.2.2 | | Microsoft.Owin.Security | <4.2.2 | 4.2.2 | | Microsoft.AspNetCore.App.Runtime.win-x64 | >=3.0.0,3.1.24 | 3.1.25 | | Microsoft.AspNetCore.App.Runtime.linux-x64 | >=3.0.0,3.1.24 | 3.1.25 | | Microsoft.AspNetCore.App.Runtime.win-x86 | >=3.0.0,3.1.24 | 3.1.25 | | Microsoft.AspNetCore.App.Runtime.osx-x64 | >=3.0.0,3.1.24 | 3.1.25 | | Microsoft.AspNetCore.App.Runtime.linux-musl-x64 | >=3.0.0,3.1.24 | 3.1.25 | | Microsoft.AspNetCore.App.Runtime.linux-arm64 | >=3.0.0,3.1.24 | 3.1.25 | | Microsoft.AspNetCore.App.Runtime.linux-arm | >=3.0.0,3.1.24 | 3.1.25 | | Microsoft.AspNetCore.App.Runtime.win-arm64 | >=3.0.0,3.1.24 | 3.1.25 | | Microsoft.AspNetCore.App.Runtime.win-arm | >=3.0.0,3.1.24 | 3.1.25 | | Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 | >=3.0.0,3.1.24 | 3.1.25 | | Microsoft.AspNetCore.App.Runtime.linux-musl-arm | >=3.0.0,3.1.24 | 3.1.25 |
.NET 5.0
| Affected packages | Affected versions | Patched versions | |---------------------------------------------------|-------------------|------------------| | Microsoft.Owin.Security.Cookies | < 4.2.2 | 4.2.2 | | Microsoft.AspNetCore.App.Runtime.win-x64 | >=5.0.0,5.0.16 | 5.0.17 | | Microsoft.AspNetCore.App.Runtime.linux-x64 | >=5.0.0,5.0.16 | 5.0.17 | | Microsoft.AspNetCore.App.Runtime.win-x86 | >=5.0.0,5.0.16 | 5.0.17 | | Microsoft.AspNetCore.App.Runtime.osx-x64 | >=5.0.0,5.0.16 | 5.0.17 | | Microsoft.AspNetCore.App.Runtime.linux-musl-x64 | >=5.0.0,5.0.16 | 5.0.17 | | Microsoft.AspNetCore.App.Runtime.linux-arm64 | >=5.0.0,5.0.16 | 5.0.17 | | Microsoft.AspNetCore.App.Runtime.linux-arm | >=5.0.0,5.0.16 | 5.0.17 | | Microsoft.AspNetCore.App.Runtime.win-arm64 | >=5.0.0,5.0.16 | 5.0.17 | | Microsoft.AspNetCore.App.Runtime.win-arm | >=5.0.0,5.0.16 | 5.0.17 | | Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 | >=5.0.0,5.0.16 | 5.0.17 | | Microsoft.AspNetCore.App.Runtime.linux-musl-arm | >=5.0.0,5.0.16 | 5.0.17 |
.NET 6.0
| Affected packages | Affected versions | Patched versions | |---------------------------------------------------|-------------------|------------------| | Microsoft.Owin.Security.Cookies | <4.2.2 | 4.2.2 | | Microsoft.AspNetCore.App.Runtime.win-x64 | >=6.0.0,6.0.4 | 6.0.5 | | Microsoft.AspNetCore.App.Runtime.linux-x64 | >=6.0.0,6.0.4 | 6.0.5 | | Microsoft.AspNetCore.App.Runtime.win-x86 | >=6.0.0,6.0.4 | 6.0.5 | | Microsoft.AspNetCore.App.Runtime.osx-x64 | >=6.0.0,6.0.4 | 6.0.5 | | Microsoft.AspNetCore.App.Runtime.linux-musl-x64 | >=6.0.0,6.0.4 | 6.0.5 | | Microsoft.AspNetCore.App.Runtime.linux-arm64 | >=6.0.0,6.0.4 | 6.0.5 | | Microsoft.AspNetCore.App.Runtime.linux-arm | >=6.0.0,6.0.4 | 6.0.5 | | Microsoft.AspNetCore.App.Runtime.win-arm64 | >=6.0.0,6.0.4 | 6.0.5 | | Microsoft.AspNetCore.App.Runtime.win-arm | >=6.0.0,6.0.4 | 6.0.5 | | Microsoft.AspNetCore.App.Runtime.osx-arm64 | >=6.0.0,6.0.4 | 6.0.5 | | Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 | >=6.0.0,6.0.4 | 6.0.5 | | Microsoft.AspNetCore.App.Runtime.linux-musl-arm | >=6.0.0,6.0.4 | 6.0.5 |
Patches
-
If you're using .NET Core 6.0, you should download and install Runtime 6.0.5 or SDK 6.0.105 (for Visual Studio 2022 v17.0) or SDK 6.0.203 (for Visual Studio 2022 v17.1) from https://dotnet.microsoft.com/download/dotnet-core/6.0.
-
If you're using .NET 5.0, you should download and install Runtime 5.0.17 or SDK 5.0.214 (for Visual Studio 2019 v16.9) or SDK 5.0.408 (for Visual Studio 2011 v16.11) from https://dotnet.microsoft.com/download/dotnet-core/5.0.
-
If you're using .NET Core 3.1, you should download and install Runtime 3.1.25 or SDK 3.1.419 (for Visual Studio 2019 v16.9 or Visual Studio 2011 16.11 or Visual Studio 2022 17.0 or Visual Studio 2022 17.1 ) from https://dotnet.microsoft.com/download/dotnet-core/3.1.
.NET 6.0, .NET 5.0 and .NET Core 3.1 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.
Other Details
- Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/220
- An Issue for this can be found at https://github.com/dotnet/aspnetcore/issues/41608
- MSRC details for this can be found at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-29117
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the availability of the system.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard