-
Notifications
You must be signed in to change notification settings - Fork 44
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
PoC Failure on Win10 - Not domain joined #10
Comments
Hi @fneur and thank you for the detailed issue. I would have time to redo the attack with your configuration in next weeks. Probable issue that I could think on top of my head:
Thank you |
@nitbx many thanks in advance for your support! I think I will try out different configurations meanwhile. Cheers, F. |
Hi @fneur I just updated everything and it seem to work with a basic MiTM attack:
For the next step, I will try to do as you did.
Thank you. |
HI @nitbx thanks for the update. Recently, I also did some further testing, where I replaced the (pywsus) server machine (which was running Win10 in my original setup) with a (virtual) Linux machine. The client stayed the same and, unfortunately, the results stayed the same. Whenever 'check for updates' is performed on the client, pywsus receives a SyncUpdates SOAP HTTP request. However, unlike the PoC, a GetExtendedUpdateInfo request is never received by pywsus. Cheers, F. |
Some more testing tonight with 2 AWS VMs (again with a direct network connection, same subnet):
Same result: PoC not working |
Hi @fneur, Just did a test and it work on my side. From the DC, I changed the GPO to put my kali as the WSUS server: After that I changed the network for the Kali and the Window10 workstation for host-only 192.168.78.0/24. Windows10 worksation: 192.168.78.130 Can you give us a Wireshark trace? I'm not sure why you have this behaviour. Thank you ! |
Here's a Wireshark capture file (wrt my original setup): Many thanks in advance for taking the time! |
Well, I see no difference except ID, time and uid... Here is the Yours:
Mine:
I guess I would need to try on AWS in order to have the exact same version as you. |
Hi @nitbx, (Note: The Thank you! |
Interesting command, didn't know about it. WindowsUpdate.log (Lots of garbage in the logs from testing) Thank you. |
Hi @nitbx, Comments / Results
Questions
Thanks, F. |
Additional info to the previous post: I also did a test after cleaning the Windows SoftwareDistribution folder (which is often recommended to troubleshoot Windows Update problems). The corresponding log file is depicted below (basically the same as in the previous post, but with an additional GetConfig call): |
Hi @fneur and thank you for the time you take to address this issue with us. For now it does not ring any bell, but I will try with a non-domain join host. After, can you show me your GPO in order to specify the WSUS. I'm not sure what you mean by:
Mine: |
I got the same issue with a non-domain joined host.
I'm confident that if we find the right UpdateID we can make it work. Still nice that we found the issue. Thank you. |
I found something. Fresh Windows 10 not domain joined but with latest update from MSFT
Fresh Windows 10 not domain joined with the latest update from MSFT. After registering with the real WSUS and performing one checks update. Then changing the local GPO for the PYWSUS server.
I will compare Wireshark traces and keep you updated. Thank you |
Hi @nitbx, thanks for your effort. I appreciate it. |
Same situation here. I can never get past Thank you |
No. Unfortunately, no positive updates on my part! |
Thanks for following up. I'm working on it when it possible. The status is that I'm confident the attack could work on a non-domain join computer. Now it just a question of finding a needle in a PCAP. |
Has there been any update on this? I'm having the same issue on a fresh installed windows 10 pro. |
No |
I am afraid I have the exacxt same problem and in a pentest the update never goes further than the syncupdate-request.... Probably the solution is to use another younger tool... Anybody found a good working alternative? |
Trying to replicate the PoC in a simple setting involving two Win10 boxes with a direct network connection (i.e., no MITM involved), the process gets stuck after the SyncUpdates phase.
Whenever 'check for updates' is performed on the client, pywsus receives a SyncUpdates SOAP HTTP request. However, unlike the PoC, a GetExtendedUpdateInfo request is never received by pywsus.
Setup
Client (Win10, 10.0.0.14 ) <----------> pywsus (Win10, 10.0.0.4, local firewall disabled)
Client
Betriebssystemname: Microsoft Windows 10 Pro
Betriebssystemversion: 10.0.19043 Nicht zutreffend Build 19043
Betriebssystemhersteller: Microsoft Corporation
Betriebssystemkonfiguration: Eigenständige Arbeitsstation
Typ des Betriebssystembuilds: Multiprocessor Free
Systemtyp: x64-based PC
Prozessor(en): 1 Prozessor(en) installiert.
[01]: Intel64 Family 6 Model 23 Stepping 10 GenuineIntel ~3003 MHz
Domain: WORKGROUP
Hotfix(es): 11 Hotfix(e) installiert.
[01]: KB5004331
[02]: KB4577266
[03]: KB4577586
[04]: KB4580325
[05]: KB4586864
[06]: KB4589212
[07]: KB4593175
[08]: KB4598481
[09]: KB5000736
[10]: KB5004237
[11]: KB5003742
PYWSUS
Betriebssystemname: Microsoft Windows 10 Pro
Betriebssystemversion: 10.0.19042 Nicht zutreffend Build 19042
Betriebssystemhersteller: Microsoft Corporation
Betriebssystemkonfiguration: Eigenständige Arbeitsstation
Typ des Betriebssystembuilds: Multiprocessor Free
Systemtyp: x64-based PC
Prozessor(en): 1 Prozessor(en) installiert.
[01]: Intel64 Family 6 Model 142 Stepping 12 GenuineIntel ~1803 MHz
Domain: WORKGROUP
Hotfix(es): 11 Hotfix(e) installiert.
[01]: KB5004331
[02]: KB4562830
[03]: KB4577266
[04]: KB4577586
[05]: KB4580325
[06]: KB4586864
[07]: KB4589212
[08]: KB4593175
[09]: KB4598481
[10]: KB5004237
[11]: KB5003742
Windows Update Client + WSUS Configuration
Client configuration via GPO
pywsus is run with simplified command line: python pywsus.py -v -H 10.0.0.4 -p 8530 -e PsExec64.exe -c "/accepteula"
Results + Output of tools
Whenever 'check for updates' is performed on the client, pywsus receives a SyncUpdates SOAP HTTP request and responds. However, a GetExtendedUpdateInfo request is never received by pywsus. After some time the client initiates a ReportEventBatch action, which is subsequently answered by pywsus.
The text was updated successfully, but these errors were encountered: