Microsoft is releasing security advisories for .NET Core and ASP.NET Core. Issues addressed by this update are summarized in the fixes section below. Details can be found in corresponding announcements in the .NET Core and ASP.NET Core repos.
.NET Core 1.1.7 and SDK 1.1.8 are available for download and usage in your environment.
The .NET Core SDK 1.1.8 includes .NET Core 1.1.7 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 1.1.8, the following command will show that you're running version 1.1.8 of the tools.
dotnet --version
Your feedback is important and appreciated. We've created an issue at dotnet/core #1341 for your questions and comments.
The .NET Core Docker images have been updated for this release. Look for the 1.1.7 images.
Deployment of this update to Azure AppServices is in process. Because AppServices is a high availability service, the deployment is carfully staged across regions over a period of time. Deployment will begin in the West US 2 and North Central US regions with remaining regions following over a few days.
Issue: Running the package manager update command on Linux systems where .NET Core has been previously installed may offer an update for dotnet-host.x86_64. If the update is allowed to proceed, .NET Core could be in a broken state as only the dotnet host is updated.
Resolution: To install the update, either the Runtime or SDK must be explicitly installed. e.g. sudo apt-get install dotnet-sharedframework-microsoft.netcore.app-1.1.7, if you only need the runtime or sudo apt-get dotnet-dev-1.1.8, to install both the SDK and Runtime.
We are working to improve our Linux packages to enable correct package manager update behavior. This work is being tracked in the following issues:
The following packages and binaries are updated by the March 2018 update:
- System.Private.Corelib
- Microsoft.NETCore.Runtime.CoreCLR
- Microsoft.NETCore.Jit
Microsoft is aware of a security vulnerability in the public versions of .NET Core where a malicious file or web request could cause a denial of service (DoS) attack. See the following announcement for details.