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
Possible Apache ActiveMQ Exploitation via Java Spawning Command Shell (via process_creation)
Malicious Veeam CVE-2023-27532 Exploitation Enabling xp_cmdshell via VeeamHax (via process_creation)
Suspicious PraisonAI Unauthenticated Config Endpoint Access via Webserver
Malicious Langflow Build Public Temp RCE Access via Webserver
Suspicious PraisonAI Vulnerability Scanner User Agent via Webserver
Malicious LiteLLM Authentication SQL Injection via Web Request (via webserver)
Possible Marimo Unauthenticated Terminal WebSocket Access via Web Request (via webserver)
Possible React2Shell Next.js Prototype Pollution Exploitation via Web Request (via webserver)
Malicious Marimo Notebook Credential File Access via Shell (via process_creation)
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.