-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ERROR] kuhl_m_misc_printnightmare_CallAddPrinterDriverEx #357
Comments
Target OS: Windows Server 2016 Datacenter (Domain Controller) |
Hi @sujit , I've only played with this recently so I'm certainly no expert. However, I found the same behavior you described when my DLL payload was getting eaten by AV. I finally crafted one that did evade AV, and when that happens, the last line of output says:
And then I found that my DLL executed and called home to my Cobalt Strike server. |
I'm getting the same CallAddPrinterDriverEx error, against both 2016 and 2019 DCs, with both having their AV disabled. Would love to hear if anyone has some insights or suggestions. Thanks! |
can you confirm that the serv can reach the share without credentials ? |
FYI, I am able to access the anonymous share records from the DC box without any authentications in-place. However, this time I see another error, but pretty much similar (error code value changed this time) though: Just curious, if at all someone has the PCAP (when the exploit actually worked), would anyone mind sharing the same? That could help me understand what might be going wrong under the hood.
@Ug0Security ^^^ |
I have the same issue on a Windows 10 without AV in a VM, I checked the code a bit, and I think 1 condition here is probably the issue (the share folder is available without credentials): mimikatz/mimikatz/modules/kuhl_m_misc.c Line 1439 in c212760
Btw I like spaghetti :p |
If you have this in your capture (between +, the "poc" is for fresh system without previous attempt, you can have better result by adding Example with previous attempt(s) of another POC
|
Have you solved this problem |
I think cube0x0/CVE-2021-1675#25 can solve the issue. Soletimes backup folder is cleanup properly, using this solution we can perform rce without bruteforcing the backup folder. It’s more stable. |
can you tell me where is calc.dll? |
So, i had this issue and have been trying to solve it for a few days. Im now able to reproduce the issue and consistently repair it. If it helps anyone else, feel free to try: 2 To restore it, go one step up in folder structure from \2\ and run: (in my case C:\SEC\2 would be C:\SEC) |
While trying to reproduce the
printnightmare
bug, I am coming across with an error condition. As per the wireshark packet traces, for theAddPrinterDriverEx
DCERPC call I don't see any potential error (screenshot attached below) though.Any idea, if I missing something here?
mimikatz exec:
Wireshark:
The text was updated successfully, but these errors were encountered: