Supported browser:
- Microsoft IE
- Mozilla Firefox
- Google Chrome
- Apple Safari
- From DHCP server.
- Request to DNS server.
- Request to WINS server
- LLMNR multicast request.
- NetBIOS Name broadcast request.
- Hosts local file.
- Lmhosts local file.
There are the following PAC file requirements if WPAD is used:
- PAC file should be located in root folder on web server.
- PAC file name should be wpad.dat.
To conduct the attack successfully an attacker should have:
Discovery Process: if the system name is "ltp.us.company.com", following is the order of query.
Attack scenario using NetBIOS/LLMNR
Services that use WPAD regardless of IE settings
Solutions:
- Specially crafted PAC file on web server.
- Rouge Proxy server controlled by the attacker;
- Tools required: SSL session hijacker, network packet analyser, etc.
Discovery Process: if the system name is "ltp.us.company.com", following is the order of query.
- Wpad.us.company.com
- Wpad.company.com
- Wpad.com
Attack scenario using NetBIOS/LLMNR
Services that use WPAD regardless of IE settings
- Windows Update Service
- Microsoft Crypto API uses it for CRL or Root CA
- Microsoft firewall client for ISA server with certain settings.
Solutions:
- Configure firewalls and proxies to log and block outbound requests for wpad.dat files.
- Consider disabling automatic proxy discovery/configuration in browsers and operating systems unless those systems will only be used on internal networks.
- Configure internal DNS servers to respond authoritatively to internal TLD queries
- Distribute PAC file thru group policy.
- Allow only authenticated updates of entries on DNS server
- Create a DNS sinkhole entry for wpad file location.
- https://findproxyforurl.com/deploying-wpad/
- https://www.websense.com/content/support/library/web/v78/wcg_help/xplctwpd.aspx
- https://www.cisco.com/c/en/us/td/docs/security/web_security/connector/connector3000/WPADAP.html
- https://googleprojectzero.blogspot.com/2017/12/apacolypse-now-exploiting-windows-10-in_18.html
- https://www.ptsecurity.com/upload/corporate/ww-en/download/wpad_weakness_en.pdf
- https://tools.ietf.org/html/draft-ietf-wrec-wpad-01
- https://kc.mcafee.com/corporate/index?page=content&id=KB90075&locale=en_US
- https://auth0.com/blog/heads-up-https-is-not-enough-when-using-wpad/
- https://securityintelligence.com/news/wpad-leaks-could-mean-flood-of-url-trouble/
- https://www.cvedetails.com/cve/CVE-2016-3213/
Comments
Post a Comment