.NET Core July 2018 Update - July 10, 2018
.NET Core 1.0.12 is available for download and usage in your environment.
Blog Round up
The .NET Core SDK 1.1.10 includes .NET Core 1.0.12 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 1.1.10, running dotnet --version will show that you're running version 1.1.10 of the .NET Core tools.
Your feedback is important and appreciated. We've created an issue at dotnet/core #1768 for your questions and comments.
Docker Images
The .NET Core Docker images have been updated for this release. Look for the updated images for .NET Core 1.0.12 and .NET Core SDK 1.1.10 and read "Staying up-to-date with .NET Container Images" for details and insights into using the .NET Core images.
Azure AppServices
- Deployment of .NET Core 1.0.12 to Azure App Services has begun. It will be available in limited regions today and expected worldwide by the end of the week.
.NET Core Lifecycle News
See .NET Core Supported OS Lifecycle Policy to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
.NET Core 2.1 is expected to be declared LTS in the next few months. It is recommended that 2.1 be the default target for projects. .NET Core 2.0 will go out of support October 2018.
Supported Linux version changes
Fedora 26 and Ubuntu 17.10 will reach end of life in July. This is the last update of .NET Core which will support these versions.
Notable Changes in 1.0.12
Microsoft Security Advisory CVE-2018-8356: .NET Core Security Feature Bypass Vulnerability
CVE-2018-8356: .NET Core Security Feature Bypass Vulnerability
Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
Microsoft is aware of a security feature bypass vulnerability that exists when .NET Core does not correctly validate certificates. An attacker who successfully exploited this vulnerability could present an expired certificate when challenged.
The update addresses the vulnerability by correcting how .NET Core applications handle certificate validation.
Package and Binary updates
| Package name | Vulnerable versions | Secure versions |
|---|---|---|
| System.Private.ServiceModel | 4.0.0, 4.1.0, 4.1.1 4.3.0, 4.3.1 4.4.0, 4.4.1, 4.4.2 4.5.0, 4.5.1 |
4.1.2 or later 4.3.2 or later 4.4.3 or later 4.5.2 or later |
| System.ServiceModel.Duplex | 4.0.0, 4.1.0, 4.1.1 4.3.0, 4.3.1 4.4.0, 4.4.1, 4.4.2 4.5.0, 4.5.1 |
4.1.2 or later 4.3.2 or later 4.4.3 or later 4.5.2 or later |
| System.ServiceModel.Http | 4.0.0, 4.1.0, 4.1.1 4.3.0, 4.3.1 4.4.0, 4.4.1, 4.4.2 4.5.0, 4.5.1 |
4.1.2 or later 4.3.2 or later 4.4.3 or later 4.5.2 or later |
| System.ServiceModel.NetTcp | 4.0.0, 4.1.0, 4.1.1 4.3.0, 4.3.1 4.4.0, 4.4.1, 4.4.2 4.5.0, 4.5.1 |
4.1.2 or later 4.3.2 or later 4.4.3 or later 4.5.2 or later |
| System.ServiceModel.Primitives | 4.0.0, 4.1.0, 4.1.1 4.3.0, 4.3.1 4.4.0, 4.4.1, 4.4.2 4.5.0, 4.5.1 |
4.1.2 or later 4.3.2 or later 4.4.3 or later 4.5.2 or later |
| System.ServiceModel.Security | 4.0.0, 4.1.0, 4.1.1 4.3.0, 4.3.1 4.4.0, 4.4.1, 4.4.2 4.5.0, 4.5.1 |
4.1.2 or later 4.3.2 or later 4.4.3 or later 4.5.2 or later |