When domain names attack: the WPAD name collision vulnerability
This is a rather technical article, but it highlights some unintended consequences of new extensions, and possible security risks. The bottom line: if your organization is using private domains like .local .network or .whatever - Watch out.
Previously inexistent extensions may now be available for sale on the market and resolve globally.
PS: the wpad trick is not the only possible example taking advantage of the technique.
Source: https://nakedsecurity.sophos.com/20...attack-the-wpad-name-collision-vulnerability/
This is a rather technical article, but it highlights some unintended consequences of new extensions, and possible security risks. The bottom line: if your organization is using private domains like .local .network or .whatever - Watch out.
Previously inexistent extensions may now be available for sale on the market and resolve globally.
PS: the wpad trick is not the only possible example taking advantage of the technique.
...A combination of poorly configured networks and new rules on internet domain names are giving cybercriminals a new and easy way to attack entire organisations, according to research out of the University of Michigan.
The vulnerability, described by US-CERT (the United States Computer Emergency Readiness Team) in alert TA16-144A issued 23 May 2016, affects computers that are using WPAD.
WPAD is short for Web Proxy Autodiscovery Protocol, a system that makes it easy for organisations to configure the many web browsers inside their network.
WPAD is supposed to find its browser configuration files on the internal network, but wily attackers may be able to trick WPAD into downloading booby-trapped versions of those configuration files from the public internet instead.
Source: https://nakedsecurity.sophos.com/20...attack-the-wpad-name-collision-vulnerability/












