.NET Core June 2020 Updates – 2.1.19 and 3.1.5
Today, we are releasing the .NET Core June 2020 Update. These updates contain security and reliability fixes. See the individual release notes for details on updated packages.
Security
CVE-2020-1108: .NET Core Denial of Service Vulnerability
To comprehensively address CVE-2020-1108, Microsoft has released updates for .NET Core 2.1 and .NET Core 3.1. Customers who use any of these versions of .NET Core should install the latest version of .NET Core. See the Release Notes for the latest version numbers and instructions for updating .NET Core.
Microsoft is aware of a denial of service vulnerability which exists when .NET Core improperly handles web requests. An attacker who successfully exploited this vulnerability could cause a denial of service against a .NET Core web application. The vulnerability can be exploited remotely, without authentication.
A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the .NET Core application. The update addresses the vulnerability by correcting how the .NET Core web application handles web requests.
Getting the Update
- .NET Core 3.1.5 and .NET Core SDK ( Download | Release Notes )
- .NET Core 2.1.19 and .NET Core SDK ( Download | Release Notes )
See the .NET Core release notes for details on the release, including issues fixed and affected packages.
The latest .NET Core updates are available on the .NET Core download page.
Docker Images
.NET Docker images have been updated for today’s release. The following repos have been updated.
- dotnet/core/sdk: .NET Core SDK
- dotnet/core/aspnet: ASP.NET Core Runtime
- dotnet/core/runtime: .NET Core Runtime
- dotnet/core/runtime-deps: .NET Core Runtime Dependencies
- dotnet/core/samples: .NET Core Samples
Note: You must pull updated .NET Core container images to get this update, with either docker pull or docker build --pull.
Visual Studio
This update will be included in a future update of Visual Studio.
Each version of Visual studio is only supported with a given version of the .NET Core SDK. Visual Studio version information is included in the .NET Core SDK download pages and release notes. If you are not using Visual Studio, we recommend using the latest SDK release.
Light
Dark
4 comments
You said that installing the SDK will also install the runtime, but does that also include the ASP.Net Core runtime?
For us using Visual Studio on Windows, should we get the 32-bit, 64 or both of the SDK?
Since I’m using Visual Studio on Windows, it looks like I need to use this page:
https://github.com/dotnet/core/blob/master/release-notes/3.1/3.1.5/3.1.301-download.md
and download the x64 version of the SDK since I’m on 64-bit Windows, correct?
When should nuget references for dotnet core/azure functions be applied? Every time I’ve tried upgrading project for the last several months I have been presented with silent breaking changes. They work fine locally but the azure functions runtime fails to start for deployed functions. After reverting to release -1 I’ve typically been able to get the functions to start.
It would be nice if we could trust release packages being compatible with their dependencies. Especially when those dependencies are all from Microsoft.
-Thanks,
Matt
https://github.com/dotnet/core/issues/3989 ,”dotnet core v3.1/3.0 Process.Start execute shell command Memory Leak”,when it will be fixed?