Coercion Attacks in Active Directory
Coercion attacks abuse Windows RPC protocols to force a target machine to authenticate outbound to a host you control. The authentication arrives as an NTLM challenge, which can be relayed to another service or captured and cracked offline. Coercing a domain controller is the most valuable target — its machine account hash can be used for DCSync, and a relay to LDAP or ADCS yields immediate domain compromise.
Coercion is the trigger. The impact depends on what you do with the arriving authentication — relay it with ntlmrelayx, capture it with Responder, or receive it on an unconstrained delegation host to extract a TGT.
Capture arriving hashes with Responder
Warning
This tool is prohibited in the OSCP exam. Responder performs LLMNR/NBT-NS/NBNS spoofing, which is explicitly listed as a prohibited technique in the OSCP exam guide. Do not use during exam environments.
When the goal is hash capture rather than relay, start Responder before triggering coercion. Responder poisons LLMNR, NBT-NS, and mDNS to intercept authentication from any host on the segment, and also listens directly for coerced connections.
[SMB] NTLMv2-SSP Hash: DC01$::CORP:a1b2c3d4e5f6:...
When using Responder alongside ntlmrelayx, disable SMB and HTTP listeners in Responder so ntlmrelayx can receive the connections instead. Edit /usr/share/responder/Responder.conf and set SMB = Off and HTTP = Off before starting Responder. See NTLM Relay for the relay workflow.
PrinterBug — MS-RPRN coercion
The Print Spooler service exposes an RPC method that forces the target to authenticate to an arbitrary host. It requires the Print Spooler service to be running on the target and any valid domain credentials to trigger. Works against DCs running Spooler — common on older environments.
SMB 10.10.10.10 445 DC01 [+] Spooler service enabled on DC01
[*] Triggering authentication via MS-RPRN RpcRemoteFindFirstPrinterChangeNotification... [*] Connecting to ncacn_np:10.10.10.10[\pipe\spoolss] [+] Triggered RPC call - incoming authentication expected on 10.10.10.20
PetitPotam — MS-EFSR coercion
PetitPotam abuses the MS-EFSR protocol (Encrypting File System Remote) to force authentication. The unauthenticated variant works on unpatched targets. The authenticated variant requires valid credentials but works on patched systems where unauthenticated EFSR is blocked.
[+] Sending auth request [+] Triggered RPC call - incoming authentication expected on 10.10.10.20
Coercer — multi-protocol coercion
Coercer wraps multiple coercion techniques including MS-RPRN, MS-EFSR, MS-FSRVP, and MS-DFSNM into a single tool. Use scan to identify which methods work against the target before triggering, then coerce to execute.
[+] MS-RPRN: RpcRemoteFindFirstPrinterChangeNotification - success [+] MS-EFSR: EfsRpcOpenFileRaw - success [+] Incoming authentication expected on 10.10.10.20
Once authentication arrives at your host, the next action depends on your setup. Responder captures it for offline cracking. ntlmrelayx forwards it to a target service — see NTLM Relay for relay targets and setup. An unconstrained delegation host receives it as a full TGT — see Kerberos Abuse for TGT extraction from that context.
References
-
krbrelayx — dirkjanm GitHubgithub.com/dirkjanm/krbrelayx (opens in new tab)
printerbug.py MS-RPRN coercion tool
-
PetitPotam — GitHubgithub.com/topotam/PetitPotam (opens in new tab)
MS-EFSR coercion, authenticated and unauthenticated variants
-
Coercer — GitHubgithub.com/p0dalirius/Coercer (opens in new tab)
Multi-protocol coercion covering MS-RPRN, MS-EFSR, MS-FSRVP, MS-DFSNM
Was this helpful?
Your feedback helps improve this page.