WPAD Name Collision Vulnerability
Below is the full text from US-CERT Technical Alert - WPAD Name Collision Vulnerability, published 23 May 2016.
- Windows, OS X, Linux systems and web browsers with WPAD enabled
- Networks using unregistered or unreserved TLDs
Web Proxy Auto-Discovery (WPAD) Domain Name System (DNS) queries that are intended for resolution on private or enterprise DNS servers have been observed reaching public DNS servers . In combination with the new generic top-level domain (gTLD) program’s incorporation of previously undelegated gTLDs for public registration, leaked WPAD queries could result in domain name collisions with internal network naming schemes  . Opportunistic domain registrants could abuse these collisions by configuring external proxies for network traffic and enabling man-in-the-middle (MitM) attacks across the internet.
|01-NOV-17||Conference Paper: Client-side Name Collision Vulnerability in the New gTLD Era: A Systematic Study (Appearing in ACM Conference on Computer and Communications Security, CCS, 2017)|
|23-MAY-16||Conference Paper: MitM Attack by Name Collision: Cause Analysis and WPAD Vulnerability Assessment in the New gTLD Era (Appearing in IEEE Security and Privacy 2016)|
|23-MAY-16||White Paper: Enterprise Remediation for WPAD Name Collision Vulnerability|
|15-SEP-13||ICANN Board Correspondence: Focused Analysis of .CBA Queries|
|05-AUG-13||Technical Report: New gTLD Security, Stability, Resiliency Update: Exploratory Consumer Impact Analysis|
|05/08/2013||ICANN Public Comment: Difference Between Apples and Oranges (Regarding name collisions in new gTLDs versus in .com and other existent top level domains)|
|28-MAR-13||Technical Report: New gTLD Security and Stability Considerations (PDF)|
WPAD is a protocol used to ensure all systems in an organisation use the same web proxy configuration. Instead of individually modifying configurations on each device connected to a network, WPAD locates a proxy configuration file and applies the configuration automatically.
The use of WPAD is enabled by default on all Microsoft Windows operating systems and internet Explorer browsers. WPAD is supported but not enabled by default on Mac OS X and Linux-based operating systems, as well as Safari, Chrome, and Firefox browsers.
Leaked WPAD queries could result in domain name collisions with internal network naming schemes. If an attacker registers a domain to answer leaked WPAD queries and configures a valid proxy, there is potential to conduct man-in-the-middle (MitM) attacks across the Internet.
- Consider disabling automatic proxy discovery/configuration in browsers and operating systems unless those systems will only be used on internal networks.
- Consider using a registered and fully qualified domain name (FQDN) from global DNS as the root for enterprise and other internal namespace.
- Consider using an internal TLD that is under your control and restricted from registration with the new gTLD program. Note that there is no assurance that the current list of “Reserved Names” list from the new gTLD Applicant Guidebook (AGB) will remain reserved with subsequent rounds of new gTLDs .
- Configure internal DNS servers to respond authoritatively to internal TLD queries.
- Configure firewalls and proxies to log and block outbound requests for wpad.dat files.
- Identify expected WPAD network traffic and monitor the public namespace or consider registering domains defensively to avoid future name collisions.
- File a report with ICANN if your system is suffering demonstrable severe harm due to name collision by visiting https://forms.icann.org/en/help/name-collision/report-problems.