Sploitus

Exploit for Deserialization of Untrusted Data in Microsoft

githubexploit Β· 2026-08-04

Exploit Code

README155 lines
## https://sploitus.com/exploit?id=BA8D9654-19F6-5C3C-8E38-D9367CADC1F2
# cve-2025-53770-research
🚨 Threat intel & incident response research on SharePoint "ToolShell" RCE zero-day (CVE-2025-53770). πŸ•΅οΈβ€β™‚οΈ Covers root-cause deserialization flaws, attack timelines, risk metrics, and defensive EDR validation playbooks. πŸ›‘οΈ
# πŸ•΅οΈ CVE-2025-53770 β€” SharePoint "ToolShell" Zero-Day Research

**Threat intel & incident response research on the Microsoft SharePoint "ToolShell" RCE zero-day.** Covers root-cause deserialization flaws, attack timelines, risk metrics, and defensive/EDR validation playbooks.

Presented by **Muhammad Farshad Abdullah Khan**

---

## πŸ“ˆ Overview

SharePoint has been Microsoft's core enterprise collaboration platform since 2001, now serving 200M+ monthly active users for document management, intranets, and workflow automation. That scale is exactly why CVE-2025-53770 is a big deal β€” a critical RCE sitting in a platform most large orgs run on-prem.

| | |
|---|---|
| 🚨 **CVE** | CVE-2025-53770 |
| πŸ”₯ **Severity** | Critical β€” CVSS 9.8 |
| βš™οΈ **Component** | ToolShell |
| πŸ›‘ **Type** | Remote Code Execution (unauthenticated) |
| πŸ“… **Discovered** | July 15, 2025 |
| πŸ“… **Disclosed** | July 19, 2025 |
| πŸ› οΈ **Affected** | SharePoint Server 2016, 2019, Subscription Edition (on-prem) |

---

## ⚠️ Vulnerability Details

- **Root cause:** Insecure deserialization of untrusted data in the ToolShell component. The server reconstructs malicious object structures from unvalidated input, enabling arbitrary command execution.
- **Exploit vector:** Specially crafted HTTP requests carrying malicious serialized payloads β€” no valid credentials required.
- **Blast radius:** Up to ~70% unauthorized control over SharePoint admin functionality once exploited; ~85% of identified attempts used crafted HTTP payloads as the delivery method.

---

## πŸ”₯ Attack Process

### 1️⃣ Reconnaissance
- Attackers scan for publicly exposed ToolShell endpoints.
- Fingerprint server versions to match known exploit paths.
- Map network perimeter for weak access controls.

### 2️⃣ Exploitation
- Malicious serialized object embedded in a normal-looking HTTP request.
- Untrusted deserialization triggers unauthenticated RCE.
- Attacker gains a foothold usable for exfiltration or lateral movement.

### 3️⃣ Persistence & Escalation
- Web shells dropped into public-facing IIS directories for durable backdoor access.
- Paired with **CVE-2025-53771** (privilege escalation) to jump from service-account level to full domain admin.
- ~75% of exploit chains include immediate web shell installs; ~60% of cases saw successful domain-admin escalation post-exploit.

---

## πŸ›‘ Impact Analysis

- **Data breach:** Exfiltration of sensitive corporate documents from compromised SharePoint sites.
- **Operational impact:** Long-term stealthy espionage rather than outages β€” attackers stayed quiet to avoid detection.
- **Strategic risk:** Loss of IP, legal docs, and confidential business data; direct hit to compliance posture.
- Shodan/Censys scans found thousands of exposed on-prem servers; ~13% of scanned enterprise environments ran vulnerable self-hosted configs, and ~6% of those left ToolShell directories completely unprotected.

**Sectors hit hardest:**
| Sector | Risk |
|---|---|
| πŸ›οΈ Government | National security data, espionage exposure |
| 🏒 Enterprise | Theft of proprietary/competitive assets |
| πŸŽ“ Academia | R&D and research partnership data exposure |

---

## πŸ”’ Detection β€” Indicators of Compromise (IoCs)

- πŸ’» **Unusual PowerShell activity** flagged by Microsoft Defender for Endpoint β€” commands deviating from baseline behavior.
- πŸ•΅οΈ **Unauthorized `.aspx` files** appearing in public-facing IIS directories β€” classic web shell signature.
- 🌐 **Anomalous outbound traffic** to unknown/blacklisted IPs β€” a strong signal of active exfiltration.

---

## πŸ›‘οΈ Microsoft Response

- Emergency patch released **July 19, 2025**, covering SharePoint Server 2016, 2019, and Subscription Edition.
- Patch restricts unauthenticated object reconstruction in ToolShell, closing the deserialization path.
- ~68% enterprise patch adoption within the first month.
- ⚠️ Residual risk: ~32% of orgs on unsupported/legacy versions remain exposed β€” no patch coverage for them.

---

## πŸ› οΈ Prevention Strategies

| Control | Effectiveness |
|---|---|
| 🚨 Immediate patch deployment | Cuts exploitation risk ~80% |
| πŸ”’ Least privilege + MFA on SharePoint admins | Blocks ~85% of attempted admin credential compromise |
| βš™οΈ Network segmentation (isolate admin interfaces) | Cuts lateral movement exposure ~70% |

---

## 🚨 Incident Response Best Practices

1. **Containment** β€” isolate infected servers within 1 hour of detection (cut infection spread ~70% in observed cases).
2. **Forensics** β€” pull system logs + memory dumps to reconstruct the attack chain (used in 85%+ of successful IR efforts).
3. **Communication** β€” notify stakeholders within 24 hours and meet breach notification obligations (linked to 90% better recovery cooperation).

---

## πŸ“Š Lessons Learned

- **~78%** of vulnerable environments had unpatched configs susceptible to the ToolShell deserialization flaw.
- **Only 22%** of orgs had real-time anomaly detection on SharePoint β€” the other 78% had delayed breach discovery.
- **~65%** of environments were exposed to this zero-day before any vendor fix existed β€” proof that patch-cycle-only defense isn't enough.

**Architecture fixes worth prioritizing:**
- πŸ’» Behavioral EDR + application controls monitoring `w3wp.exe` (the IIS worker process) to block unauthorized process spawning.
- πŸ“ˆ AI-driven behavioral analytics for continuous ToolShell activity monitoring.
- πŸ› οΈ Quarterly red team exercises simulating ToolShell-style exploitation.

---

## βš™οΈ Comparative Case: CVE-2023-29357 vs CVE-2025-53770

| | CVE-2023-29357 | CVE-2025-53770 |
|---|---|---|
| **Mechanism** | Auth bypass via bad JWT validation | Insecure deserialization in ToolShell |
| **Outcome** | Auth bypass β†’ RCE | Immediate persistent web shell deployment |
| **Detection** | Sometimes flagged via auth event logs | Frequently bypasses standard traffic anomaly filters |

Both are unauthenticated RCE at admin-level privilege β€” same severity ceiling, different plumbing.

---

## πŸ•΅οΈ Attack Flow Diagram

```
Recon β†’ Exploit β†’ Persist β†’ Escalate β†’ Exfiltrate
```

- **Tools used:** serialized payloads, crafted HTTP requests, web shells
- **Detection points:** IIS access logs, EDR/endpoint alerts, file integrity monitoring

---

## πŸ“‚ Repo Contents

- `README.md` β€” this write-up
- Presentation slides (PDF) β€” full deck with charts and stats referenced above

---

## ⚠️ Disclaimer

This repository is for **defensive research and educational purposes only** β€” threat intel summary, detection guidance, and mitigation strategy. It does not contain exploit code or working attack tooling.

---

**Author:** Muhammad Farshad Abdullah Khan