Microsoft is investigating two reported Zero Day vulnerabilities currently undergoing exploitation that affect Microsoft Exchange Server 2013, 2016, and 2019.

The first vulnerability, CVE-2022-41040, is a server-side request forgery (SSRF) vulnerability, while the second, CVE-2022-41082, allows remote code execution (RCE) when PowerShell is accessible to the attacker.

“Microsoft is aware of limited targeted attacks using the two vulnerabilities to get into users’ systems. In these attacks, CVE-2022-41040 can enable an authenticated attacker to remotely trigger CVE-2022-41082,” Microsoft said in an blog post. “It should be noted that authenticated access to the vulnerable Exchange Server is necessary to successfully exploit either of the two vulnerabilities.”

The software giant then added it was working on an “accelerated timeline to release a fix.” They provided mitigation and detection guidance to help protect against attacks.

Schneider Bold

Microsoft Exchange Online has detections and mitigations in place to protect customers. Microsoft is also monitoring these already deployed detections for malicious activity and will take necessary response actions to protect customers.

Microsoft Exchange online customers do not need to take any action. Those on premises Microsoft Exchange customers should review and apply the following URL Rewrite Instructions and block exposed Remote PowerShell ports.

The current mitigation adds a blocking rule in “IIS Manager -> Default Web Site -> URL Rewrite -> Actions” to block the known attack patterns.

The following URL Rewrite Instructions, which are currently being discussed publicly, are successful in breaking current attack chains.

  1. Open the IIS Manager
  2. Expand the Default Web Site
  3. In the Feature View, click URL Rewrite
  4. In the Actions pane on the right-hand side, click Add Rules
  5. Select Request Blocking and click OK
  6. Add String “.*autodiscover\.json.*\@.*Powershell.*” (excluding quotes) and click OK
  7. Expand the rule and select the rule with the Pattern “.*autodiscover\.json.*\@.*Powershell.*” and click Edit under Conditions
  8. Change the condition input from {URL} to {REQUEST_URI}

There is no known impact to Exchange functionality if the URL Rewrite module is installed as recommended.

In terms of detections, Microsoft said it does not currently have a specific detection query for this issue. However, the Exchange SSRF Autodiscover ProxyShell detection, created in response to ProxyShell, can be used for queries as there are similarities in function with this threat. Also, there is an Exchange Server Suspicious File Downloads query which specifically looks for suspicious downloads in IIS logs.

Click here for more on the Microsoft blog post.

Pin It on Pinterest

Share This