High severity vulnerability that affects System.Management.Automation
Published 13 Sept 2019 · Updated 2 Apr 2025
Is your project on an affected System.Management.Automation?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=6.2.0 <6.2.3
- Fixed in
- 6.2.3
dotnet add package System.Management.Automation --version 6.2.3- Affected
- >=6.0.0 <6.1.6
- Fixed in
- 6.1.6
dotnet add package System.Management.Automation --version 6.1.6Details
Microsoft Security Advisory CVE-2019-1301: Denial of Service Vulnerability in PowerShell Core
Executive Summary
A denial of service vulnerability exists when PowerShell Core or .NET Core improperly handles web requests. An attacker who successfully exploited this vulnerability could cause a denial of service against a PowerShell Core scripts.
The update addresses the vulnerability by correcting how the .NET Core handles web requests.
System administrators are advised to update PowerShell Core to an unaffected version (see [affected software](#user-content-affected-software).)
Discussion
Please open a support question to discussion the PowerShell aspects of this advisory. Please use dotnet/announcements#121 for discussion of the .NET aspects this advisory.
<a name="affected-software">Affected Software</a>
The vulnerability affects PowerShell Core prior to the following versions:
| PowerShell Core Version | Fixed in | |-------------------------|-------------------| | 6.1 | 6.1.6 | | 6.2 | 6.2.3 | | 7.0 | unaffected | |5 | unaffected |
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](#user-content-affected-software) to see if your version of PowerShell Core is affected.
1. If you are running a version of PowerShell Core where the executable is not pwsh or pwsh.exe, then you are affected. This only existed for preview version of 6.0.
How do I update to an unaffected version?
Follow the instructions at Installing PowerShell Core to install the latest version of PowerShell Core.
Other Information
Reporting Security Issues
If you have found a potential security issue in PowerShell Core, 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 Core and install the previous version of PowerShell Core. This should be treated as a temporary measure. Therefore, the script or module should be updated to work with the patched version of PowerShell Core.
Acknowledgments
Paul Ryman of VMware Sydney Engineering Team
Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure.
See acknowledgments for more information.
External Links
Is GHSA-62gw-3rmj-wmp2 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected System.Management.Automation, and gives you the command that fixes it.
More advisories for System.Management.Automation
- MediumCVE-2019-1167System.Management.Automation subject to bypass via script debugging · 17 Jul 2019
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.