DNS Poisoning
Another method that can be used to launch this attack is to compromise a DNS server. One method for doing so is known as DNS poisoning. DNS poisoning exploits a vulnerability in early versions of the Berkeley Internet Name Daemon (BIND). BIND, the most commonly deployed DNS software on the Internet, was developed for BSD UNIX. A network of Internet BIND servers translates native Internet IP addresses to the commonly used names such as www.ggu.edu for Golden Gate University. Prior to version 8.1 of BIND, it was possible to "poison" the table entries of a DNS server with false information.
The information could include a false IP address for a DNS entry in the server's table. The result could be that when someone used that DNS server to "resolve" the URL name, he or she would be directed to the incorrect IP address.
By compromising a DNS server, a hacker can make a legitimate URL point to the hacker's Web site. The Web surfer might enter in www.amazon.com expecting to go to the Amazon.com Web site to purchase a book. The URL www.amazon.com normally points to xxx.xxx.xxx.xxx, but the hacker has compromised a DNS server to point that URL to his or her server. As a result, the Web surfer is brought to the hacker's site and not to Amazon.com.
In this tutorial:
- Threats and Attacks
- The OSI Reference Model
- TCP/IP Protocol Suite
- Threats, Vulnerabilities, and Attacks
- Attacks
- Viruses
- Worm
- Trojan Horses
- Trap Doors
- Logic Bombs
- Port Scanning
- Spoofs
- Sequence Number Spoofing
- DNS
- DNS Poisoning
- Redirects
- Password Cracking
- Sniffing
- War Dialing
- Denial of Service
- Ping of Death
- SYN Flooding
- SPAM
- Smurf Attack
