How severe is GHSA-jcmq-5rrv-j2g4?

GHSA-jcmq-5rrv-j2g4 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-jcmq-5rrv-j2g4?

GHSA-jcmq-5rrv-j2g4 affects the following packages: PowerShell (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-jcmq-5rrv-j2g4?

Update PowerShell to 7.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jcmq-5rrv-j2g4 is resolved across your whole dependency graph.

How do I detect GHSA-jcmq-5rrv-j2g4 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for PowerShell. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-jcmq-5rrv-j2g4 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-jcmq-5rrv-j2g4?

O3 pinpoints whether GHSA-jcmq-5rrv-j2g4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-jcmq-5rrv-j2g4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jcmq-5rrv-j2g4 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-jcmq-5rrv-j2g4 published, and has it been updated?

GHSA-jcmq-5rrv-j2g4 was published on February 2, 2024 and was last updated on November 28, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

GHSA-jcmq-5rrv-j2g4

HIGH

PowerShell is subject to remote code execution vulnerability

Published

Feb 2, 2024

Updated

Nov 28, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

.NETPowerShell

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

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:

Run pwsh -v, then, check the version in the table in Affected Software to see if your version of PowerShell is affected.
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 [email protected].

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

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

Version 1.0 Last Updated 2020-03-10

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`PowerShell`	all versions	7.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for PowerShell. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update PowerShell to 7.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jcmq-5rrv-j2g4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-jcmq-5rrv-j2g4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-jcmq-5rrv-j2g4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

# 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.

O3 Security · Impact-Aware SCA

Is GHSA-jcmq-5rrv-j2g4 in your dependencies?

O3 detects GHSA-jcmq-5rrv-j2g4 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works