Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Search

GHSA-jcmq-5rrv-j2g4

HighCVSS 8.8 / 10
Published Feb 2, 2024·Last modified Nov 28, 2024
Affected Components(0)

No affected components available

Description

Microsoft Security Advisory CVE-2020-0605: .NET Framework Remote Code Execution Vulnerability

Executive Summary

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. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

Exploitation of the vulnerability requires that a user open a specially crafted file with an affected version of .NET Framework. 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 Framework checks the source markup of a file.

Discussion

Please open a support question to discuss the PowerShell aspects of this advisory. Please use https://github.com/dotnet/wpf/issues/2424 for discussion of the .NET WPF aspects of this advisory.

<a name="affected-software">Affected Software</a>

The vulnerability affects PowerShell prior to the following versions:

| PowerShell Core Version | Fixed in | |-------------------------|-------------------| | 6.2 | Not Affected | | 7.0 | 7.0.0 |

Advisory FAQ

How do I know if I am affected?

If all of the following are true:

  1. Run pwsh -v, then, check the version in the table in Affected Software to see if your version of PowerShell is affected.
  2. If you are running a version of PowerShell where the executable is not pwsh or pwsh.exe, then you are affected. This only existed for preview version of 7.0.

How do I update to an unaffected version?

Follow the instructions at Installing PowerShell to install the latest version of PowerShell.

Other Information

Reporting Security Issues

If you have found a potential security issue in PowerShell, please email details to secure@microsoft.com.

Support

You can ask questions about this issue on GitHub in the PowerShell organization. This is located at https://github.com/PowerShell/. The Announcements repo (https://github.com/PowerShell/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue where you can ask questions.

What if the update breaks my script or module?

You can uninstall the newer version of PowerShell and install the previous version of PowerShell. This should be treated as a temporary measure. Therefore, the script or module should be updated to work with the patched version of PowerShell.

Acknowledgments

Soroush Dalili (@irsdl)

External Links

CVE-2020-0605

Revisions

<!-- TBD: update date -->

V1.0 (March 10, 2020): Advisory published.

Version 1.0 Last Updated 2020-03-10

Risk Scores
Base Score
8.8

The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. The attacker needs the user to perform some action, like clicking a link. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a high impact on the integrity of the data. There is a high impact on the availability of the system.

Threat Intelligence
8.1

Exploitation activity has been observed. Apply available patches or mitigations urgently.

EPSS
N/A

Probability that this vulnerability will be exploited in the wild within the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard