Windows Application Error 1000 with lsass.exe and WLDAP32.dll Indicating LDAP Nightmare Attempt (CVE-2024-49113)

Alerts on Windows Application Error (EventID 1000) showing lsass.exe crashing in WLDAP32.dll—potential CVE-2024-49113 exploitation attempt.

FreeReviewedSigma · High · v5
Product
windows
Service
application
Author
Samuel Monsempes (SigmaHQ), DRL 1.1
Published
2025-01-08
Updated
2026-07-31

ATT&CK techniques

Impact
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

What it detects

This rule flags Windows Application Error (EventID 1000) events where the recorded faulting process is lsass.exe and the faulting module is WLDAP32.dll, with Provider_Name set to Application Error. Such a crash/exception in these components can be triggered during exploitation activity matching the “LDAP Nightmare” pattern tied to CVE-2024-49113. It relies on application error telemetry that includes the provider name, event id, and the faulting process/module values in event data.

Related detections3 linkedT1499 — drag to rearrange
Malicious Panamorfi DDoS JAR Execution via Java (via process_creation)
Windows: Detect LSASS crashes caused by netlogon.dll stack buffer overrun (STATUS_STACK_BUFFER_OVERRUN)
Linux auditd: Detect writes to /proc/sysrq-trigger or sysrq-related config for Magic SysRq abuse
Windows Application Error 1000 with lsass.exe and WLDAP32.dll Indicating LDAP Nightmare Attempt (CVE-2024-49113)
Pivot detection · T1499 · 3 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.