-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microsoft Security Advisory CVE-2020-1147 | .NET Core Remote Code Execution Vulnerability #39296
Comments
These versions look suspect to me since 3.1.5 runtime / 3.1.301 SDK are "current". |
Does this vulnerability also affect .Net core 2.2 applications? |
@Noppey 2.2 is no longer supported and we do not provide patches for it. See https://dotnet.microsoft.com/download/dotnet-core for the current support matrix. |
Microsoft Security Advisory CVE-2020-1147 | .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 an XML file. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user.
A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to an ASP.NET Core application, or other application that parses certain types of XML.
The security update addresses the vulnerability by restricting the types that are allowed to be present in the XML payload.
Discussion
Announcement for this issue can be found at dotnet/announcements#159
Mitigation factors
Microsoft has not identified any mitigating factors for this vulnerability.
Affected software
Please note that .NET Core 3.0 is now out of support and all applications should be updated to 3.1.
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 3.1. If you have installed one or more .NET Core SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio which will also update your .NET Core SDKs.
You can list the versions you have installed by running the
dotnet --info
command. You will see output like the following;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 secure@microsoft.com. 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.
External Links
CVE-2020-1147
Revisions
V1.0 (July 14, 2020): Advisory published.
Version 1.0
Last Updated 2020-07-14
The text was updated successfully, but these errors were encountered: