search

bb00 / zer0dump

Abuse CVE-2020-1472 (Zerologon) to take over a domain and then repair the local stored machine account password.
176 stars 44 forks source link

Using port 139 throws: "socket.gaierror: [Errno -5] No address associated with hostname" #3

Open NeodymiumFerBore opened 4 years ago

NeodymiumFerBore commented 4 years ago

Running the exploit using port 139 throws the following error:

socket.gaierror: [Errno -5] No address associated with hostname

(My DNS is set up correctly, I'm able to resolve DC1, dc1.lab.lan, reverse lookup 10.0.0.10)

Same result by specifying -target_machine. Full command: ./zer0dump.py -port 139 -target_machine DC1 DC1. Tried multiple combinations, using IP, fqdn or NetBIOS. I don't know much about Netlogon, hard to troubleshoot for me.

Appart that, no problem with port 445.

Full trace:

Traceback (most recent call last):
  File "/opt/test/CVE-2020-1472_ZeroLogon-zer0dump/zer0dump/zer0dump.py", line 163, in <module>
    perform_attack(options)
  File "/opt/test/CVE-2020-1472_ZeroLogon-zer0dump/zer0dump/zer0dump.py", line 81, in perform_attack
    rpc_con, serverChallenge = try_zero_authenticate(dc_handle, dc_ip, target_computer)
  File "/opt/test/CVE-2020-1472_ZeroLogon-zer0dump/zer0dump/zer0dump.py", line 31, in try_zero_authenticate
    rpc_con.connect()
  File "/opt/test/CVE-2020-1472_ZeroLogon-zer0dump/venv/lib/python3.8/site-packages/impacket/dcerpc/v5/rpcrt.py", line 801, in connect
    return self._transport.connect()
  File "/opt/test/CVE-2020-1472_ZeroLogon-zer0dump/venv/lib/python3.8/site-packages/impacket/dcerpc/v5/transport.py", line 342, in connect
    af, socktype, proto, canonname, sa = socket.getaddrinfo(self.getRemoteHost(), self.get_dport(), 0, socket.SOCK_STREAM)[0]
  File "/usr/lib/python3.8/socket.py", line 918, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -5] No address associated with hostname

Note: using impacket 0.9.22.dev1+20200915.115225.78e8c8e4 instead of the one in your requirements.txt. It was throwing other errors at zer0dump runtime.