Question 1

What is the potential impact of CVE-2020-1472?

Accepted Answer

The successful exploitation of CVE-2020-1472 allows an attacker to impersonate any computer on the network, disable security features that protect the Netlogon process, and change a computer’s password associated with its Active Directory account.

Question 2

What does an attacker need to exploit Zerologon?

Accepted Answer

In order to exploit Zerologon an attacker needs to be on the network. The attacker can gain access to networks by multiple means such as phishing, drive-by exploits, or additional means.

Question 3

What event ids are enabled once the August 2020 patch is installed on a domain controller?

Accepted Answer

The following event ids are enabled once the August 2020 patch is installed on a Domain Controller:

Log event IDs 5827 and 5828 log when a connection has been denied to the domain controller once enforcement mode has been enabled.
Log event IDs 5830 and 5831 log when a connection is allowed by the “Domain controller: Allow vulnerable Netlogon secure channel connections” group policy.
Log event IDs 5829 logs whenever a vulnerable Netlogon secure channel connection is allowed for both Windows and Non-Windows devices.

Question 4

What actions can I take to protect my devices from the Zerologon Vulnerability?

Accepted Answer

deepwatch recommends taking the following actions in vulnerable environments to assist in further protecting devices:

Action 1: Patch all systems with Microsoft’s August 2020 security updates and verify the successful installation with a vulnerability scanning tool, such as those from Qualys or Tenable, and your organization’s patch management tools.
Action 2: Enabling forwarding to SIEM devices or monitoring event id 5829 and monitoring for devices that are not utilizing a secure Netlogon.

If a device is detected with event id 5829 recommended steps by Microsoft are as follows:

Windows Systems
– Confirm the device(s) are running supported versions of Windows
– Ensure the system is fully updated.
– Check to ensure that Domain member: digitally encrypt or sign secure channel data (always) is set to enabled.
For non-windows systems acting as a Domain Controller and an event is logged
– Ensure the non-compliant DC supports secure RPC with Netlogon secure channel then enable secure RPC on the DC.
– If the non-compliant DC does not support RPC then the device manufacturer (OEM) or software vendor will need to update in order to support secure RPC with Netlogon secure channel.
– Remove the non-compliant DC.
If a non-compliant DC cannot support the RPC with Netlogon secure channel before the DCs are in enforcement mode, add the DC using the “Domain controller: allow vulnerable Netlogon secure channel connections” group policy. Further information on this action can be found at the following location on Microsoft’s site:
https://support.microsoft.com/en-us/help/4557222/how-to-manage-the-changes-in-netlogon-secure-channel-connections-assoc
Action 3: Enable DC enforcement mode after confirming all devices are compliant and will not break as a result of enabling. It should be noted the patch to be released February 9th, 2021 will automatically enable enforcement mode on Domain Controllers.

Advancing the SOC

The Managed Security Platform For The Cyber Resilient Enterprise

Cultivating Cyber Resilience Experts

Get access to all the critical information you need to be successful

Deepwatch ATI Annual Threat Report 2024

Oracle WebLogic Vulnerability

What is the Potential Impact?

Oracle WebLogic Vulnerability Mitigation

Detecting CVE-2020-16898 and CVE-2020-16899

Supporting information

Subscribe to the Deepwatch Insights Blog