Replies: 4 comments
-
I know this is very recent, but the new versions are missing from the download links. |
Beta Was this translation helpful? Give feedback.
-
They're publishing as I type this. |
Beta Was this translation helpful? Give feedback.
-
@blowdart You mean .NET Core 3.1 app running on .NET Core 3.1.0 is not affected by this vulnerability? |
Beta Was this translation helpful? Give feedback.
-
@SIkebe 3.1 apps are also affected, and have been fixed via #2428. @blowdart this language may need to be updated here as well as in #2424. |
Beta Was this translation helpful? Give feedback.
-
Microsoft Security Advisory CVE-2020-0606 : .NET Core Remote Code Execution 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 remote code execution vulnerability exists in .NET software when the software fails to check the source markup of a file. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user.
Exploitation of the vulnerability requires that a user open a specially crafted file with an affected version of .NET Core. In an email attack scenario, an attacker could exploit the vulnerability by sending the specially crafted file to the user and convincing the user to open the file.
The security update addresses the vulnerability by correcting how .NET Core checks the source markup of a file.
Announcement
The original announcement for this issue can be found at dotnet/announcements#149
Mitigation factors
Microsoft has not identified any mitigating factors for this vulnerability.
Affected software
Any .NET Core application running on .NET Core 3.0.0, 3.0.1 or 3.1.0.
How do I know if I am affected?
If you have a runtime or SDK with a version listed in affected software you are exposed to the vulnerability.
How do I fix the issue?
To fix the issue please install the latest version of .NET Core. If you have multiple versions of .NET Core installed you will need to install multiple runtimes, or SDKs depending on what you have installed.
You can list the versions you have installed by running the
dotnet --info
command. You will see output like the following;If you have both 3.0 and 3.1 installed, you need to install the updates for both versions.
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 Core, please email details to [email protected]. Reports may qualify for the .NET Core Bug Bounty. Details of the .NET Core Bug Bounty including terms and conditions are at https://aka.ms/corebounty.
Support
You can ask questions about this issue on GitHub in the .NET Core 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.
Acknowledgments
Soroush Dalili (@irsdl)
External Links
CVE-2020-0606
Revisions
V1.1 (January 16, 2020): Clarified versions.
V1.0 (January 14, 2020): Advisory published.
Version 1.1
Last Updated 2020-01-16
Beta Was this translation helpful? Give feedback.
All reactions