CVE-2020-1472: Microsoft Netlogon Privilege Escalation
Microsoft Netlogon · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.
- CVSS v3.1 (CVE record)
- 5.5
- medium
- EPSS (exploit probability, 30 days)
- 99.3%
- among the highest 0.1% of all CVEs
- Added to CISA KEV
- 2021-11-03
- US federal due date 2022-05-03
- Ubuntu priority
- medium
What is CVE-2020-1472?
An elevation of privilege vulnerability exists when an attacker establishes a vulnerable Netlogon secure channel connection to a domain controller, using the Netlogon Remote Protocol (MS-NRPC). An attacker who successfully exploited the vulnerability could run a specially crafted application on a device on the network.
To exploit the vulnerability, an unauthenticated attacker would be required to use MS-NRPC to connect to a domain controller to obtain domain administrator access. Microsoft is addressing the vulnerability in a phased two-part rollout. These updates address the vulnerability by modifying how Netlogon handles the usage of Netlogon secure channels.
For guidelines on how to manage the changes required for this vulnerability and more information on the phased rollout, see How to manage the changes in Netlogon secure channel connections associated with CVE-2020-1472 (updated September 28, 2020). When the second phase of Windows updates become available in Q1 2021, customers will be notified via a revision to this security vulnerability.
If you wish to be notified when these updates are released, we recommend that you register for the security notifications mailer to be alerted of content changes to this advisory. See Microsoft Technical Security Notifications.
CISA required action: Apply updates per vendor instructions.
CISA notes
- Reference CISA's ED 20-04 (cisa.gov/news-events/directives/ed-20-04-mitigate-netlogo…) for further guidance and requirements. Note: The due date for addressing this vulnerability aligns with the requirements outlined in ED 20-04. nvd.nist.gov/vuln/detail/CVE-2020-1472
Upstream versions (CVE record)
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Windows Server version 2004x64AffectedFixed in
- builds before the security update of 2020-08-11
- security update of 2020-08-11
- Microsoft Windows Server 2019x64AffectedFixed in
- builds before the security update of 2020-08-11
- security update of 2020-08-11
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- builds before the security update of 2020-08-11
- security update of 2020-08-11
- Microsoft Windows Server, version 1909 (Server Core installation)x64AffectedFixed in
- builds before the security update of 2020-08-11
- security update of 2020-08-11
- Microsoft Windows Server, version 1903 (Server Core installation)x64AffectedFixed in
- builds before the security update of 2020-08-11
- security update of 2020-08-11
- Microsoft Windows Server 2016x64AffectedFixed in
- builds before the security update of 2020-08-11
- security update of 2020-08-11
- Microsoft Windows Server 2016 (Server Core installation)x64AffectedFixed in
- builds before the security update of 2020-08-11
- security update of 2020-08-11
- Microsoft Windows Server 2008 R2 Service Pack 1x64AffectedFixed in
- builds before the security update of 2020-08-11
- security update of 2020-08-11
- Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64AffectedFixed in
- builds before the security update of 2020-08-11
- security update of 2020-08-11
- Microsoft Windows Server 2012x64AffectedFixed in
- builds before the security update of 2020-08-11
- security update of 2020-08-11
- Microsoft Windows Server 2012 (Server Core installation)x64AffectedFixed in
- builds before the security update of 2020-08-11
- security update of 2020-08-11
- Microsoft Windows Server 2012 R2x64AffectedFixed in
- builds before the security update of 2020-08-11
- security update of 2020-08-11
- Microsoft Windows Server 2012 R2 (Server Core installation)x64AffectedFixed in
- builds before the security update of 2020-08-11
- security update of 2020-08-11
- Microsoft Windows Server version 20H2x64AffectedFixed in
- builds before the security update of 2020-08-11
- security update of 2020-08-11
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows Server version 2004x64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows Server, version 1909 (Server Core installation)x64 |
|
|
| Microsoft Windows Server, version 1903 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
| Microsoft Windows Server 2016 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2008 R2 Service Pack 1x64 |
|
|
| Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2012x64 |
|
|
| Microsoft Windows Server 2012 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2012 R2x64 |
|
|
| Microsoft Windows Server 2012 R2 (Server Core installation)x64 |
|
|
| Microsoft Windows Server version 20H2x64 |
|
|
Ubuntu and Debian releases
A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.
Ubuntu 20.04 LTS·samba
Fixed: 2:4.11.6+dfsg-0ubuntu1.5
Ubuntu 18.04 LTS·samba
Fixed: 2:4.7.6+dfsg~ubuntu-0ubuntu2.20
Ubuntu 16.04 LTS·samba
ESM ended
Fixed: 2:4.3.11+dfsg-0ubuntu0.16.04.31
Ubuntu 14.04 LTS·samba
fix via Ubuntu Pro
Fixed: 2:4.3.11+dfsg-0ubuntu0.14.04.20+esm9
Check and fix on a server
Run on each Ubuntu or Debian server. Replace samba with the source package from the table above.
1. Show installed packages built from the source package, with their versions
dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="samba"'2. Compare each installed version with the fixed version for your release from the table
I=INSTALLED_VERSION; F=FIXED_VERSION # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac3. Install the fix
sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="samba"{print $1}')Services keep running the old code until they are restarted – restart the affected service or check with needrestart.
Rows marked “fix via Ubuntu Pro”: these fixes are only installable with an Ubuntu Pro subscription (ESM). Attach the machine first (sudo pro attach, then sudo pro enable esm-infra esm-apps), then run the commands above.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-330
References
Other advisories
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.