Windows: Detect Microsoft Exchange CVE-2020-0688 exploitation via Eventlog errors

Identifies Exchange Control Panel error events containing a ViewState parameter consistent with CVE-2020-0688 exploitation attempts.

FreeReviewedSigma · High · v5
Product
windows
Service
application
Author
Florian Roth (Nextron Systems), wagga (SigmaHQ), DRL 1.1
Published
2020-02-29
Updated
2026-07-31

ATT&CK techniques

Initial Access
  1. Recon

  2. Resource Dev

  3. Execution

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags Windows application log entries where the Microsoft Exchange Control Panel provider emits an Error event (EventID 4) and the record contains a ViewState parameter marker. An attacker exploiting CVE-2020-0688 may generate crafted Exchange requests that cause these error conditions to be logged. It relies on Windows Application event telemetry including EventID, Provider_Name, Level, and the presence of the '&__VIEWSTATE=' string in the event data.

Related detections9 linkedT1190 — drag to rearrange
Malicious Node.js Process Spawning Unix Shell or Network Client
Malicious SharePoint ToolShell Exploitation via ToolPane Endpoint
Malicious Exchange Mailbox Export to ASPX via New-MailboxExportRequest
Suspicious Shell Spawned by ActiveMQ Java Process
Cleo Autorun Exploitation via Healthcheck File Drop
Suspicious SharePoint Worker Process Spawning Command Interpreter via ToolShell
Malicious IIS Worker Process Spawning Command Shell Reconnaissance
Potential StyleSmuggler (CVE-2026-75650) Exploitation Attempt - Magento GraphQL Styles Parameter (via webserver)
Cisco IOS XE Configuration Change by Web UI WSMA User
Windows: Detect Microsoft Exchange CVE-2020-0688 exploitation via Eventlog errors
Pivot detection · T1190 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.