| Package | Affected versions | Patched versions |
|---|---|---|
| Microsoft.AspNetCore.Components | ≥ 6.0.0, < 6.0.25≥ 7.0.0, < 7.0.14≥ 8.0.0-rc.2.23480.2, < 8.0.0 | 6.0.257.0.148.0.0 |
| .net | = 8.0.0≥ 6.0.0, < 6.0.25≥ 7.0.0, < 7.0.14 | 6.0.257.0.14 |
| asp.net core | = 8.0.0≥ 6.0.0, < 6.0.25≥ 7.0.0, < 7.0.14 | 6.0.257.0.14 |
| visual studio 2022 | ≥ 17.2, < 17.2.22≥ 17.4, < 17.4.14≥ 17.6, < 17.6.10≥ 17.7, < 17.7.7 | 17.2.2217.4.1417.6.1017.7.7 |
Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 6.0, ASP.NET Core 7.0 and, ASP.NET Core 8.0 RC2. This advisory also provides guidance on what developers can do to update their applications to address this vulnerability.
A security feature bypass vulnerability exists in ASP.NET where an unauthenticated user is able to bypass validation on Blazor server forms which could trigger unintended actions.
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/288
This vulnerability only affects ASP.NET Core Blazor apps. Other application types, including ASP.NET Core apps which do not utilize Blazor, are not affected.
If your application uses the following package versions, ensure you update to the latest version of .NET.
| Package name | Affected version | Patched version |
|---|---|---|
| Microsoft.AspNetCore.Components | 8.0.0-rc.2.23480.2 | 8.0.0 |
| Package name | Affected version | Patched version |
|---|---|---|
| Microsoft.AspNetCore.Components | >= 7.0.0, < 7.0.13> | 7.0.14 |
| Package name | Affected version | Patched version |
|---|---|---|
| Microsoft.AspNetCore.Components |
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free| >= 6.0.0, < 6.0.24 |
| 6.0.25 |
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.
dotnet --info command. You will see output like the following;.NET Core SDK (reflecting any global.json):
Version: 7.0.200
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\7.0.300\
Host (useful for support):
Version: 76.0.5
Commit: 8473146e7d
.NET Core SDKs installed:
7.0.200 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
.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.
If you have found a potential security issue in .NET 8.0 or .NET 7.0 or .NET 6.0, please email details to [email protected]. 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.
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.
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.
V1.0 (November 14, 2023): Advisory published.
Version 1.0
Last Updated 2023-11-14