Know every vulnerabilitybefore 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.
GHSA-5frh-8cmj-gc59
No affected components available
Microsoft Security Advisory CVE-2019-1167: Windows Defender Application Control Security Feature Bypass Vulnerability
Microsoft Security Advisory CVE-2019-1167: Windows Defender Application Control Security Feature Bypass Vulnerability
Executive Summary
A security feature bypass vulnerability exists in Windows Defender Application Control (WDAC) which could allow an attacker to bypass WDAC enforcement. An attacker who successfully exploited this vulnerability could circumvent PowerShell Core Constrained Language Mode on the machine.
To exploit the vulnerability, an attacker would first have access to the local machine where PowerShell is running in Constrained Language mode. By doing that an attacker could leverage script debugging to abuse signed modules in an unintended way.
The update addresses the vulnerability by correcting how PowerShell functions in Constrained Language Mode. System administrators are advised to update PowerShell Core to an unaffected version (see affected software.)
Discussion
Please use PowerShell/PowerShell#TBD for discussion of 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.5 | | 6.2 | 6.2.2 |
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 Core is affected. - If you are running a version of PowerShell Core where the executable is not
pwshorpwsh.exe, then you are affected. This only existed for preview version of6.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
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
Revisions
V1.0 (July 16, 2019): Advisory published.
Version 1.0 Last Updated 2019-07-16
The vulnerability requires local access to the device to be exploited. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker needs high-level or administrative privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information.
Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard