CVE-2019-1167: System.Management.Automation System.Management.Automation Subject To Bypass Vulnerability
MODERATECVE-2019-1167 is a MODERATE (CVSS 4.1) system.management.automation subject to bypass vulnerability (General Security Weakness) affecting System.Management.Automation libraries in the NuGet ecosystem. The issue involves system.management.automation subject to bypass via script debugging. Remediation is available by upgrading affected packages to version 6.2.2, 6.1.5.
CVE-2019-1167 at a Glance
Security Impact
CVSS: 4.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N).
How to Fix CVE-2019-1167
To remediate this vulnerability, upgrade all affected System.Management.Automation dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade System.Management.Automation to 6.2.2
Upgrade System.Management.Automation to 6.1.5
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for System.Management.Automation
How to Check if You Are Affected
To determine whether your application is affected by CVE-2019-1167, inspect your project dependencies for System.Management.Automation:
inspect dependencies for System.Management.Automation
Analyze the terminal output to locate any version of System.Management.Automation in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 6.2.2), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under General Security Weakness. In System.Management.Automation, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2019-1167 Affected System.Management.Automation Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
System.Management.Automation
|
NuGet |
≥ 6.2.0
< 6.2.2
|
6.2.2
|
|
System.Management.Automation
|
NuGet |
≥ 6.1.0
< 6.1.5
|
6.1.5
|
References
Frequently Asked Questions
What is CVE-2019-1167?
Which System.Management.Automation versions are affected?
What version fixes CVE-2019-1167?
Is System.Management.Automation affected?
What is the CVSS score of CVE-2019-1167?
What CWE is associated with CVE-2019-1167?
How can I check NuGet dependencies for CVE-2019-1167?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-5frh-8cmj-gc59",
"modified" : "2022-09-17T01:02:30Z",
"published" : "2019-07-17T19:14:18Z",
"aliases" : [ "CVE-2019-1167" ],
"summary" : "System.Management.Automation subject to bypass via script debugging",
"details" : "## Microsoft Security Advisory CVE-2019-1167: Windows Defender Application Control Security Feature Bypass Vulnerability\n\n# Microsoft Security Advisory CVE-2019-1167: Windows Defender Application Control Security Feature Bypass Vulnerability\n\n## Executive Summary\n\nA security feature bypass vulnerability exists in Windows Defender Application Control (WDAC) which could allow an attacker to bypass WDAC enforcement.\nAn attacker who successfully exploited this vulnerability could circumvent PowerShell Core Constrained Language Mode on the machine.\n\n To exploit the vulnerability,\nan attacker would first have access to the local machine where PowerShell is running in Constrained Language mode.\nBy doing that an attacker could leverage script debugging to abuse signed modules in an unintended way.\n\nThe update addresses the vulnerability by correcting how PowerShell functions in Constrained Language Mode.\nSystem administrators are advised to update PowerShell Core to an unaffected version (see [affected software](#user-content-affected-software).)\n\n## Discussion\n\nPlease use PowerShell/PowerShell#TBD for discussion of this advisory.\n\n## <a name=\"affected-software\">Affected Software</a>\n\nThe vulnerability affects PowerShell Core prior to the following versions:\n\n| PowerShell Core Version | Fixed in |\n|-------------------------|-------------------|\n| 6.1 | 6.1.5 |\n| 6.2 | 6.2.2 |\n\n## Advisory FAQ\n\n### How do I know if I am affected?\n\nIf all of the following are true:\n\n1. 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.\n1. 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`.\n\n### How do I update to an unaffected version?\n\nFollow the instructions at [Installing PowerShell Core](https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-powershell?view=powershell-6) to install the latest version of PowerShell Core.\n\n## Other Information\n\n### Reporting Security Issues\n\nIf you have found a potential security issue in PowerShell Core,\nplease email details to secure@microsoft.com.\n\n### Support\n\nYou can ask questions about this issue on GitHub in the PowerShell organization.\nThis is located at https://github.com/PowerShell/.\nThe Announcements repo (https://github.com/PowerShell/Announcements)\nwill contain this bulletin as an issue and will include a link to a discussion issue where you can ask questions.\n\n### What if the update breaks my script or module?\n\nYou can uninstall the newer version of PowerShell Core and install the previous version of PowerShell Core.\nThis should be treated as a temporary measure.\nTherefore, the script or module should be updated to work with the patched version of PowerShell Core.\n\n### Acknowledgments\n\nMicrosoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure.\n\nSee [acknowledgments](https://portal.msrc.microsoft.com/en-us/security-guidance/acknowledgments) for more information.\n\n### External Links\n\n[CVE-2019-1167](https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1167)\n\n### Revisions\n\nV1.0 (July 16, 2019): Advisory published.\n\n*Version 1.0*\n*Last Updated 2019-07-16*",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "NuGet",
"name" : "System.Management.Automation"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "6.2.0"
}, {
"fixed" : "6.2.2"
} ]
} ]
}, {
"package" : {
"ecosystem" : "NuGet",
"name" : "System.Management.Automation"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "6.1.0"
}, {
"fixed" : "6.1.5"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/PowerShell/PowerShell/security/advisories/GHSA-5frh-8cmj-gc59"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2019-1167"
}, {
"type" : "ADVISORY",
"url" : "https://github.com/advisories/GHSA-5frh-8cmj-gc59"
}, {
"type" : "WEB",
"url" : "https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1167"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2020-06-16T21:09:07Z",
"nvd_published_at" : null
}
}