My Current Background on the topic
DHCP Spoofing is done by a rogue DHCP server on the network which replies to DHCP requests from hosts(Attacker can run a DHCP starvation attack on the legitimate DHCP server to stop it from handing away IP addresses).
The rogue server can spoof the gateway & DNS servers therefor all DNS & Traffic going away from local subnet will start to flow to the attacker. The attacker then forward the received traffic accordingly so the hosts won’t notice any disruption in connectivity and effectively pulling off a MITM attack.
In ARP Poisoning, attacker send spoofed arp messages to the network and arp cache of the switch will have wrong information so the switch starts to send traffic to the attacker (which should originally go to another host or default gateway)
DHCPDISCOVER, DHCPOFFER, DHCPREQUEST & DHCPACK are broadcast messages so typically all hosts in the local subnet will receive all this messages anyway. Even if the attacker has already done some ARP poisoning on the local subnet it won’t affect the process of DHCP.
ARP is used for resolving Internet layer addresses into link layer addresses.Since ahost does not have an IP address until DHCP process is completed ARP attacks seems useless on DHCP
My Question
As per my understanding These two attacks are two different ways that can be used to achieve same results. But I need to clarify this without any doubt.
Is there any way you can pull off a DHCP Spoofing attack by using ARP poisoning?
Continue reading What is the role of ARP poisoning when doing a DHCP spoofing attack→