Microsoft Security Advisory CVE-2022-38013: .NET Denial of Service Vulnerability

[dcwhittaker]

Executive summary

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core 3.1 and .NET 6.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

A denial of service vulnerability exists in ASP.NET Core 3.1 and .NET 6.0 where a malicious client could cause a stack overflow which may result in a denial of service attack when an attacker sends a customized payload that is parsed during model binding.

Discussion

The announcement for this issue can be found at dotnet/announcements#234

Mitigation factors

Microsoft has not identified any mitigating factors for this vulnerability.

Affected software

• Any .NET 6.0 application running on .NET 6.0.8 or earlier.
• Any ASP.NET Core 3.1 application running on .NET Core 3.1.28 or earlier.
  If your application uses the following package versions, ensure you update to the latest version of .NET.

.NET Core 3.1

Package name	Affected version	Patched version
Microsoft.AspNetCore.App.Runtime.linux-arm	>= 3.1.0, < 3.1.29	3.1.29
Microsoft.AspNetCore.App.Runtime.linux-arm64	>= 3.1.0, < 3.1.29	3.1.29
Microsoft.AspNetCore.App.Runtime.linux-musl-arm64	>= 3.1.0, < 3.1.29	3.1.29
Microsoft.AspNetCore.App.Runtime.linux-musl-x64	>= 3.1.0, < 3.1.29	3.1.29
Microsoft.AspNetCore.App.Runtime.linux-x64	>= 3.1.0, < 3.1.29	3.1.29
Microsoft.AspNetCore.App.Runtime.osx-x64	>= 3.1.0, < 3.1.29	3.1.29
Microsoft.AspNetCore.App.Runtime.win-arm	>= 3.1.0, < 3.1.29	3.1.29
Microsoft.AspNetCore.App.Runtime.win-arm64	>= 3.1.5, < 3.1.29	3.1.29
Microsoft.AspNetCore.App.Runtime.win-x64	>= 3.1.0, < 3.1.29	3.1.29
Microsoft.AspNetCore.App.Runtime.win-x86	>= 3.1.0, < 3.1.29	3.1.29

.NET 6

Package name	Affected version	Patched version
Microsoft.AspNetCore.App.Runtime.linux-arm	>= 5.0.0, < 6.0.9	6.0.9
Microsoft.AspNetCore.App.Runtime.linux-arm64	>= 5.0.0, < 6.0.9	6.0.9
Microsoft.AspNetCore.App.Runtime.linux-musl-arm	>= 5.0.1, < 6.0.9	6.0.9
Microsoft.AspNetCore.App.Runtime.linux-musl-arm64	>= 5.0.0, < 6.0.9	6.0.9
Microsoft.AspNetCore.App.Runtime.linux-musl-x64	>= 5.0.0, < 6.0.9	6.0.9
Microsoft.AspNetCore.App.Runtime.linux-x64	>= 5.0.0, < 6.0.9	6.0.9
Microsoft.AspNetCore.App.Runtime.osx-arm64	>= 6.0.0, < 6.0.9	6.0.9
Microsoft.AspNetCore.App.Runtime.osx-x64	>= 5.0.0, < 6.0.9	6.0.9
Microsoft.AspNetCore.App.Runtime.win-arm	>= 5.0.0, < 6.0.9	6.0.9
Microsoft.AspNetCore.App.Runtime.win-arm64	>= 5.0.0, < 6.0.9	6.0.9
Microsoft.AspNetCore.App.Runtime.win-x64	>= 5.0.0, < 6.0.9	6.0.9
Microsoft.AspNetCore.App.Runtime.win-x86	>= 5.0.0, < 6.0.9	6.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 Core 3.1. 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 have .NET Core 3.1 or greater installed, you can list the versions you have installed by running the dotnet --info command. You will see output like the following;
• If you are using one of the affected packages, please update to the patched version listed above.

.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

• If you're using .NET 6.0, you should download and install Runtime 6.0.9 or SDK 6.0.109 (for Visual Studio 2022 v17.1) from https://dotnet.microsoft.com/download/dotnet-core/6.0.
• If you're using .NET Core 3.1, you should download and install Runtime 3.1.29 (for Visual Studio 2019 v16.9) from https://dotnet.microsoft.com/download/dotnet-core/3.1.
  .NET 6.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.
  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 Core 3.1, 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.

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-2022-38013

Revisions

V1.0 (September 13, 2022): Advisory published.
Version 1.0
Last Updated 2022-09-13

[monty241]

Please note that the update KB5017500: 2022-09 Preview-version of cumulative update for .NET Framework 3.5, 4.8 and 4.8.1 as well as KB5017903 and KB5017915 will be processed through Windows Update. This update is currently applying to development workstations, which one-by-one after being applied are no longer capable of compiling our source code due to StackOverflowException. In addition, VS 17.2.3 and 17.3.4 crash within 60 seconds on open due to maybe incremental compilation.

Initially, we thought that upgrade to 17.3.4 was the cause, but it spontaneously started appearing on 17.2 machines too exactly on the same day the patches were installed. On a build machine, building sometimes fails now with StackOverflowException depending on software version.

Ofcourse, the vulnerability given on https://www.deskmodder.de/blog/2022/09/14/net-6-0-9-und-net-core-3-1-29-korrigieren-eine-schwere-sicherheitsluecke-cve-2022-38013/ mentions a stack overflow, but it seems unlikely that all were compromised leading to a StackOverflow directly after the patches being applied.

Both development machines and build machine are in isolated environments which are not accessible from outside, located in three unrelated network zones.

Possibly related issues:

• https://developercommunity.visualstudio.com/t/Project-open-closes-immediately/10156330
• https://developercommunity.visualstudio.com/t/Visual-Studio-2022-Closes-Without-Any-Er/10155266

[ghost]

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog clean. If you believe there is a concern related to the ASP.NET Core framework, which hasn't been addressed yet, please file a new issue.

This issue will be locked after 30 more days of inactivity. If you still wish to discuss this subject after then, please create a new issue!