Security

ToolShell – Patch, Then Hunt

If you run on-premises Microsoft SharePoint Server, stop reading after this paragraph and check your patch status. Microsoft has confirmed active exploitation of CVE-2025-53770, a critical (CVSS 9.8) unauthenticated remote code execution flaw nicknamed ToolShell, along with a related bug, CVE-2025-53771. CISA added CVE-2025-53770 to its Known Exploited Vulnerabilities catalogue on 20 July. SharePoint Online in Microsoft 365 isn’t affected.

How We Got Here

  • In May, researchers chained two SharePoint bugs (CVE-2025-49704 and CVE-2025-49706) at Pwn2Own Berlin. The chain was called “ToolShell”.
  • Microsoft fixed them in the 8 July Patch Tuesday release.
  • From around 18 July, Eye Security and others saw attackers exploiting variants that bypassed those fixes.
  • On 19–20 July, Microsoft issued new CVEs, emergency updates for SharePoint Subscription Edition and 2019 (2016 followed), and guidance.

Why “Patch, Then Hunt”

The early attacks stole ASP.NET machine keys from SharePoint servers. With those keys, an attacker can forge trusted requests even after you’ve patched. So:

  1. Patch with the latest out-of-band updates for your version.
  2. Rotate the machine keys and restart IIS, as Microsoft advises.
  3. Enable AMSI integration and endpoint protection on SharePoint servers.
  4. Hunt. Look for unexpected .aspx files, unusual w3wp.exe child processes and suspicious POSTs, using the indicators vendors have published. If you find anything, treat it as an incident, not a ticket.
  5. Ask whether SharePoint should be on the internet at all.

As an interesting aside, this week marks one year since the CrowdStrike outage. If you missed them, my posts Blue Friday and Twenty-One Fields are still a good read. And Friday is SysAdmin Day again. Patch first, then cake. 🙂

More Information