Possible CVE-2023-23397 Outlook Forced Authentication via Outbound LDAP (via network_connection)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
network_connection
Author
HuntRule
Published
2026-06-25
Updated
2026-08-28

ATT&CK techniques

Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects a Windows host initiating an outbound LDAP or Global Catalog connection to a non-private external address, which is anomalous because directory traffic normally stays inside the enterprise. Exploitation of CVE-2023-23397 can direct a client to an external LDAP endpoint as part of the forced authentication chain against Microsoft Outlook. Traffic to an external directory service indicates possible credential coercion or beaconing and warrants investigation.

Related detections9 linkedT1187 — drag to rearrange
Possible Progress WhatsUp Gold Path Traversal and UNC Coercion via core API (via webserver)
Masquerading Certificate Services Outbound LDAP or SMB Connection via Certighost Coercion (via network_connection)
Possible CVE-2023-23397 Outlook Forced Authentication via Outbound SMB (via network_connection)
Windows Process Creation: curl.exe Using NTLM with Empty Username (-u :)
WebDAV Remote Payload Retrieval via Rundll32 DavSetCookie
Windows Process Creation: Command-Line Kerberos Coercion Signature via DNS SPN Spoofing
Zeek DNS detects base64 credential target pattern consistent with Kerberos DNS object spoofing
Windows DNS Query with Kerberos Coercion Signature via DNS Object SPN Spoofing
Windows Suspicious .library-ms File Creation by 7z.exe, winrar.exe, or explorer.exe
Possible CVE-2023-23397 Outlook Forced Authentication via Outbound LDAP (via network_connection)
Pivot detection · T1187 · 9 related

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