5.5 Medium
CVSS3
Attack Vector
LOCAL
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
NONE
Availability Impact
NONE
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
9.3 High
CVSS2
Access Vector
NETWORK
Access Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:N/AC:M/Au:N/C:C/I:C/A:C
0.322 Low
EPSS
Percentile
96.9%
The Microsoft Windows Netlogon Remote Protocol (MS-NRPC) reuses a known, static, zero-value initialization vector (IV) in AES-CFB8 mode. This allows an unauthenticated attacker to impersonate a domain-joined computer, including a domain controller, and potentially obtain domain administrator privileges.
The Microsoft Windows Netlogon Remote Protocol (MS-NRPC) is a core authentication component of Active Directory that provides authentication for user and computer accounts. MS-NRPC uses an initialization vector (IV) of 0 (zero) in AES-CFB8 mode when authenticating computer accounts.
Zerologon: Unauthenticated domain controller compromise by subverting Netlogon cryptography (CVE-2020-1472) describes how this cryptographic failure allows a trivial statistical attack on the MS-NRPC authentication handshake:
> The ComputeNetlogonCredential function, however, defines that this IV is fixed and should always consist of 16 zero bytes. This violates the requirements for using AES-CFB8 securely: its security properties only hold when IVs are random.
>
> …
>
> When encrypting a message consisting only of zeroes, with an all-zero IV, there is a 1 in 256 chance that the output will only contain zeroes as well.
By choosing a client challenge and ClientCredential of all zeros, an attacker has a 1 in 256 chance of successfully authenticating as any domain-joined computer. By impersonating a domain controller, an attacker can take additional steps to change a computer’s Active Directory password (Exploit step 4: changing a computer’s AD password) and potentially gain domain administrator privileges (Exploit step 5: from password change to domain admin).
Because Samba has implemented the MS-NRPC protocol as it has been designed by Microsoft, Samba domain controllers are also affected by this vulnerability.
An unauthenticated attacker with network access to a domain controller can impersonate any domain-joined computer, including a domain controller. Among other actions, the attacker can set an empty password for the domain controller’s Active Directory computer account, causing a denial of service, and potentially allowing the attacker to gain domain administrator privileges.
The compromise of Active Directory infrastructure is likely a significant and costly impact.
On August 11, 2020, Microsoft issued an advisory that provides updates for this vulnerability.
The August 2020 updates for CVE-2020-1472 include changes to domain controllers that can optionally be enabled to require secure RPC for Netlogon secure channel connections. The changes to require secure RPC must be made to receive the most complete protection from this vulnerability. For systems that have the August 2020 update for CVE-2020-1472, enabling secure RPC enforcement mode will change domain controller behavior to require Netlogon secure channel connections using secure MS-NRPC. This change to enable enforcement mode will be deployed automatically on or after February 9, 2021.
Microsoft acknowledges Tom Tervoort of Secura for reporting this vulnerability.
This document was written by Eric Hatleback, Art Manion, and Will Dormann.
490028
Filter by status: All Affected Not Affected Unknown
Filter by content: __ Additional information available
__ Sort by: Status Alphabetical
Expand all
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Affected |
---|
We have not received a statement from the vendor.
Updated: 2020-09-17 CVE-2020-1472 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-10-01
Statement Date: September 29, 2020
CVE-2020-1472 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-21
Statement Date: September 18, 2020
CVE-2020-1472 | Affected |
---|---|
Vendor Statement: | |
HardenedBSD is not affected. |
HardenedBSD provides Samba as a third-party package, not installed by default.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2020-09-16 Updated: 2020-09-16 CVE-2020-1472 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-10-01
Statement Date: September 28, 2020
CVE-2020-1472 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2020-09-15 Updated: 2020-09-21
Statement Date: September 16, 2020
CVE-2020-1472 | Affected |
---|
Samba domain controllers (AD and NT4-like) can be impacted by the ZeroLogon CVE-2020-1472 vulnerability, but supported versions are not impacted in the default configuration.
Samba, like Microsoft, suggest that "server schannel = yes"
must be set for secure operation. This is Samba’s equivalent to Microsoft’s FullSecureChannelProtection=1
registry key.
The key difference between Samba and Microsoft Windows is that it’s already enabled by default in all Samba major versions released since March 2018 (Samba 4.8 and later).
There seem to be some legacy software, which still requires "server schannel = auto"
. Samba will soon add additional hardening that will allow administrators to use "server schannel = yes"
globally and define exceptions only for specified computer accounts.
Samba’s progress can be monitored via this bug: https://bugzilla.samba.org/show_bug.cgi?id=14497
Samba requires secure Netlogon connections by default since version 4.8. Versions of Samba prior to 4.8 are vulnerable by default. Samba versions 4.8 and later are vulnerable if they are configured to override the server schannel default value to “auto” or “no”.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-18
Statement Date: September 17, 2020
CVE-2020-1472 | Affected |
---|
Synology confirms the Synology Directory Server is affected and has published a security advisory Synology-SA-20:21 to respond to CVE-2020-1472.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Affected |
---|
We have not received a statement from the vendor.
Updated: 2020-09-17 CVE-2020-1472 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-21
Statement Date: September 21, 2020
CVE-2020-1472 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-28
Statement Date: September 25, 2020
CVE-2020-1472 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2020-09-18 Updated: 2020-09-21
Statement Date: September 19, 2020
CVE-2020-1472 | Not Affected |
---|
FreeBSD does not include support for MS-NRPC in the base system. Users who install third-party software (e.g. Samba) from ports or packages may be affected.
Notified: 2020-09-17 Updated: 2021-03-19
Statement Date: March 18, 2021
CVE-2020-1472 | Not Affected |
---|
Only AD domain controller implementations are potentially at risk, as detailed in the linked paper. (DC server “NetLogon” functions are the attack surface for this vulnerability.) We do not implement a domain controller, therefore we are NOT VULNERABLE.
We are AFFECTED, because our AD clients will need adjustment to a world that fixes this vulnerability, however. See https://www.illumos.org/issues/13169 It is now fixed in illumos upstream.
Notified: 2020-09-17 Updated: 2021-03-19
Statement Date: March 18, 2021
CVE-2020-1472 | Not Affected |
---|---|
Vendor Statement: | |
Only AD domain controller implementations are potentially at risk, as detailed in the linked paper. (DC server “NetLogon” functions are the attack surface for this vulnerability.) We do not implement a domain controller, therefore we are not vulnerable. |
Only AD domain controller implementations are potentially at risk, as detailed in the linked paper. (DC server “NetLogon” functions are the attack surface for this vulnerability.) We do not implement a domain controller, therefore we are NOT VULNERABLE to the attack.
We are AFFECTED insofar as illumos SMB/CIFS clients will need to be adjusted to interoperate with DCs that address this vulnerability.
https://www.illumos.org/issues/13169
This illumos issue has been fixed in upstream illumos.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2020-09-17 Updated: 2020-09-17 CVE-2020-1472 | Unknown |
---|
We have not received a statement from the vendor.
View all 52 vendors __View less vendors __
CVE IDs: | CVE-2020-1472 |
---|---|
Date Public: | 2020-09-16 Date First Published: |
blog.rapid7.com/2020/09/14/cve-2020-1472-zerologon-critical-privilege-escalation/
docs.microsoft.com/en-us/openspecs/windows_protocols/ms-nrpc/13db7494-6d2c-4448-be8f-cb5ba03e95d6
github.com/CERTCC/PoC-Exploits/tree/master/cve-2020-1472
github.com/dirkjanm/CVE-2020-1472
github.com/gentilkiwi/mimikatz/releases/tag/2.2.0-20200916
github.com/nccgroup/nccfsas/tree/main/Tools/SharpZeroLogon
github.com/SecuraBV/CVE-2020-1472
nakedsecurity.sophos.com/2020/09/17/zerologon-hacking-windows-servers-with-a-bunch-of-zeros/
portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-1472
support.microsoft.com/en-us/help/4557222/how-to-manage-the-changes-in-netlogon-secure-channel-connections-assoc
techcommunity.microsoft.com/t5/microsoft-365-defender/zerologon-is-now-detected-by-microsoft-defender-for-identity-cve/ba-p/1734034
www.samba.org/samba/docs/current/man-html/smb.conf.5.html#SERVERSCHANNEL
www.samba.org/samba/security/CVE-2020-1472.html
www.secura.com/pathtoimg.php?id=2055
5.5 Medium
CVSS3
Attack Vector
LOCAL
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
NONE
Availability Impact
NONE
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
9.3 High
CVSS2
Access Vector
NETWORK
Access Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:N/AC:M/Au:N/C:C/I:C/A:C
0.322 Low
EPSS
Percentile
96.9%