The Exchange Server Hack: Why You Can't Put Off Patching

From the archive: this article was written in 2021 and reflects the technology and threats of that time. For current advice, see our latest articles or ask us directly.

If your business runs its own Microsoft Exchange email server, this is the post to read first. In early March, Microsoft confirmed that a chain of serious flaws in on-premises Exchange Server is being actively exploited, and not just against big targets. Attackers have been scanning the entire internet and breaking into whatever they can reach, including small offices that didn't think anyone would bother with them.

We've already fielded calls about it from businesses across Pinellas and Pasco. So let's keep this plain: if you have an on-premises Exchange server, you need to act now, not next week.

What actually happened

The attack is being called ProxyLogon. It's a set of vulnerabilities in Exchange Server 2013, 2016, and 2019 that, chained together, let an attacker reach your server over the internet and run commands on it without a valid password. In other words, they don't need to steal a login. The bug lets them walk in.

Once inside, the common pattern is to drop what's called a web shell, a small hidden file that gives the attacker a back door. That back door stays open even after you patch, which is the part a lot of people miss. Patching closes the original hole, but it does not remove a back door that's already there.

Why small businesses are getting caught

This isn't a careful, targeted campaign aimed at Fortune 500 companies. Attackers automated it. They scanned the whole internet looking for vulnerable Exchange servers and hit everything that answered, including law offices, medical practices, contractors, and shops that happen to host their own mail. The size of your company didn't protect you. Having a public-facing Exchange server is what put you on the list.

What to do right now

Order matters here. Patching alone is not enough if you were already compromised.

  • Apply Microsoft's emergency Exchange updates immediately. Microsoft released out-of-band security updates for the affected versions. They should be installed as soon as possible, ahead of your normal patch schedule.
  • Assume you may have been hit, and check. Microsoft and CISA published tools and instructions to scan Exchange for signs of compromise, including the web shells attackers leave behind. Run them. A clean patch on a server that already has a back door gives you false comfort.
  • Look at what's exposed to the internet. If your Exchange admin interfaces are reachable from anywhere in the world, that's part of the problem. Restricting access helps.
  • Reset credentials if you find evidence of intrusion. Passwords and keys an attacker could have grabbed should be changed.

If any of this is over your head, that's normal, and it's exactly the kind of thing our cybersecurity and server administration teams handle. The risk with this one is the delay, so don't sit on it waiting to figure it out alone.

The bigger question: should you still run your own mail server?

This incident is a good moment to ask an honest question. When you host Exchange in your own server closet, you own every part of keeping it patched, monitored, and locked down. The day a flaw like this drops, the responsibility to respond within hours is entirely yours.

A lot of small businesses simply don't have someone watching for security bulletins on a Tuesday night. That's not a knock on them. It's just the reality of running a five or twenty person company where everyone has a real job already.

Moving email to a hosted service like Microsoft 365 shifts the patching and infrastructure burden to a provider whose entire business is keeping that platform secure. You still have to manage accounts, logins, and permissions, but you're no longer personally responsible for racing to patch a server before the internet finds it. For many of the businesses we support, that tradeoff makes sense, and we walk through it as part of our cloud solutions conversations.

To be clear, moving to the cloud is not an emergency response to this hack. If you're vulnerable today, patch and check for compromise first. The cloud question is the longer-term decision you make once the fire is out.

What this should teach all of us

Two lessons stand out, and they apply even if you don't run Exchange.

First, patching is not optional maintenance you get to the way you eventually get to that squeaky door hinge. When a critical security update lands, the window between "patch available" and "attackers exploiting it everywhere" can be days. Having a plan for who applies updates, and how fast, is part of running a business today.

Second, anything you expose to the internet is something you have to defend. Mail servers, remote desktop, cameras, file shares. If it's reachable from the outside, assume someone is knocking on it.

This is the kind of ongoing watchfulness that managed IT services exist to provide, so a flaw announced on a Wednesday morning doesn't become a breach by the weekend. If you're not sure whether your Exchange server is patched, or whether it was already touched, reach out and we'll help you check.

Need help with this?

Talk to a local IT team that has supported businesses across Pinellas & Pasco County since 2010.

Get a Free Consultation Free Security Assessment