Most security patches are routine. They fix something obscure, you install them on the usual schedule, and life goes on. Every so often, though, a flaw comes along that is serious enough to skip the line. Zerologon is one of those, and if your business runs a Windows server that handles logins, it applies to you.
On September 18, the federal Cybersecurity and Infrastructure Security Agency (CISA) issued an emergency directive ordering federal agencies to patch it over a single weekend. Emergency directives are rare. When the government's own cyber agency says "drop everything," small businesses should pay attention too.
What a domain controller is, in plain English
If your office uses Windows and people log in to their computers with a company username and password, you almost certainly have a domain controller. It is the server running Active Directory, the master directory of every user, every password, every computer, and every permission on your network.
Think of it as the building's key office. It decides who gets in, which doors they can open, and which files they can see. Whoever controls the domain controller effectively controls the whole network.
What Zerologon does
Zerologon is the nickname for a vulnerability tracked as CVE-2020-1472. It lives in Netlogon, a behind-the-scenes Windows protocol that computers use to authenticate with the domain controller. Microsoft rated it critical, and it received the highest possible severity score.
The researchers at Secura who discovered it published the technical details in mid-September. The short version: because of a flaw in how Netlogon handles encryption, an attacker who can reach your domain controller over the network can impersonate a trusted computer, reset the domain controller's own machine password, and from there take over the domain. No username or password is required. It can take just a few seconds.
With Zerologon, an attacker who gets onto your network does not need to steal anyone's password. They can go straight for the key office.
Once proof-of-concept code was published, the clock started ticking fast. Microsoft has since said it is seeing attackers actively trying to exploit the flaw.
"But the attacker has to be on my network already"
That is true, and it is the most common reason people shrug this one off. Zerologon generally is not something an attacker fires at your server from across the internet. They need a foothold inside first.
Unfortunately, getting that foothold is the easy part. One employee clicks a phishing link, one laptop gets infected, one weak remote access password gets guessed. Normally that initial break-in is contained to a single machine or account, and a good security setup has time to catch it. Zerologon removes that time. It turns "one infected PC" into "the attacker owns everything" almost instantly, which is exactly the path ransomware crews want before they encrypt a whole office.
The fix, and the catch
The good news: Microsoft released the first fix on August 11, as part of that month's Patch Tuesday updates. If your domain controllers have received the August 2020 cumulative update (or anything newer), the initial protection is in place.
A few important details for whoever manages your servers:
- Patch every domain controller, not just one. If you have two or three, an unpatched one is still an open door.
- Windows Server 2008 R2 is a problem. It reached end of support in January, so it only receives this fix if you are paying for Extended Security Updates. If a domain controller is still running 2008 R2 without ESU, it is time to replace it.
- This is a two-phase fix. Microsoft's August update starts the protection, but full enforcement is scheduled for a later update in early 2021. Microsoft's guidance includes watching the domain controller event logs for devices that are still making vulnerable connections, so they can be updated before enforcement arrives.
- Other devices may be affected. Some non-Windows systems that act as domain controllers, such as certain Samba-based devices, have their own fixes. If you have a NAS or appliance joined to your domain in an unusual role, check with the vendor.
Why patches like this get missed
Servers are often the last things patched in a small business, and for understandable reasons. Rebooting the domain controller can interrupt everyone's work. Nobody wants to be the person who broke logins on a Tuesday morning. So updates get postponed "until the weekend," and then the next weekend, and then they are forgotten.
We also often see offices where the server was set up years ago by someone who has since moved on, and nobody is quite sure whether updates are installing at all. That is exactly the kind of blind spot a flaw like Zerologon exploits. A clear, regular server patching routine, with a maintenance window everyone knows about, takes the drama out of it.
What to do now
- List every domain controller on your network, including any older backup DCs sitting in a closet.
- Confirm each one has the August 2020 security update or newer installed. Do not assume; check.
- Retire or upgrade any domain controller running Windows Server 2008 R2 or older without Extended Security Updates.
- Review the Netlogon-related event log entries Microsoft describes and fix any devices flagged as making vulnerable connections.
- Plan for the enforcement update coming in early 2021 so it is not a surprise.
- Tighten the front door, too: multi-factor authentication on email and remote access, and current endpoint protection on every PC.
- Put server updates on a recurring schedule instead of handling them when someone remembers.
Zerologon is fixable, and the fix is already available. The businesses at risk are simply the ones that have not installed it yet. If you are not sure where your servers stand, or you would rather have someone else handle patching on a steady schedule, we are happy to take a look. Email us at info@pinellasit.com or use our contact form.
