MS-RPRN abuse (PrinterBug)
Theory
Microsoft’s Print Spooler is a service handling the print jobs and other various tasks related to printing. An attacker controling a domain user/computer can, with a specific RPC call, trigger the spooler service of a target running it and make it authenticate to a target of the attacker's choosing. This flaw is a "won't fix" and enabled by default on all Windows environments (more info on the finding).
The coerced authentications are made over SMB. But MS-RPRN abuse can be combined with WebClient abuse to elicit incoming authentications made over HTTP which heightens NTLM relay capabilities.
The "specific call" mentioned above is the RpcRemoteFindFirstPrinterChangeNotificationEx
notification method, which is part of the MS-RPRN protocol. MS-RPRN is Microsoft’s Print System Remote Protocol. It defines the communication of print job processing and print system management between a print client and a print server.
Practice
Remotely checking if the spooler is available can be done with SpoolerScanner (Powershell) or with rpcdump (Python).
The spooler service can be triggered with printerbug or SpoolSample (C#). There are many alternatives available publicly on the Internet.
rpcdump
We can check if the spooler service is available on a target using rpcdump.py from impacket.
rpcdump.py $TARGET | grep -A 6 "spoolsv"
NetExec
NetExec (Python) can be used to check if the spooler service is running.
netexec smb <TARGET> -u <USER> -p <PASSWORD> -M spooler
netexec smb <TARGET> -u <USER> -p <PASSWORD> --local-auth -M spooler
SpoolerScanner
Check if the spooler service is available (Windows) using SpoolerScanner (Powershell)
.\SpoolerScan.ps1
Resources
Last updated
Was this helpful?