It installs a rogue DHCP server on the infected machine and listens for DHCP requests and responds with its own crafted DHCP offer packets. The reply contains malicious DNS servers, which will redirect hosts to infected websites that include everything from phishing to exploit-and-infect pages.
The question is how to protect and prevent such attacks. Here is my compiled checklist:
http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/12.1/12ew/configuration/guide/dhcp.pdf
This is an example of enabling DHCP Snooping on a Cisco Switch:
switch(config)# ip dhcp snooping
!Enables DHCP Snooping globally!
switch(config)# ip dhcp snooping vlan
!Enables DHCP Snooping for Specific VLANs!
switch(config-if)# ip dhcp snooping trust
!Sets the interface to trusted state; can then pass DHCP replies!
switch(config-if)# ip dhcp snooping limit rate
4) Use " DHCPLOC Utility" to detect rogue DHCP servers on your network, Get it from here (http://technet2.microsoft.com/windowsserver/en/library/8fa42e83-ec08-4a9b-9057-8909f7ed433e1033.mspx?mfr=true)
With this tool, you can determine which DHCP servers are available to a DHCP client and to detect unauthorized DHCP servers on a subnet.
5) Use " DhcpExplorer" , it’s a tool that allows you to discover DHCP servers on your local subnet or LAN. This is useful for locating servers that are not supposed to be on your network (rogue DHCP servers) as well as checking the expected output of known servers. The tool is designed with a user-friendly interface and is easy to use. Download it from here:
http://www.filesland.com/companies/Nsasoft-LLC/download/DhcpExplorer.exe
7) If you are a Microsoft shop, make sure that you have configured authorized DHCP server correctly, read here for more details:
http://technet.microsoft.com/en-us/library/cc781697.aspx
8) If you use Nmap, and you should by the way. You can scan your network for hosts that listen to port 67. See this example:
nmap -sU -P0 -p 67-68 -oN dhcp-scan-results > 192.168.0-3.*
Replace 192.168.0-3.* with your network's IP range.
9) Snort, is your watch dog while you are busy. Modify your snort.conf file to add a new servers list, like this:
var Authorized_DHCP [1.1.1.1,2.2.2.2]
replace 1.1.1.1, 2.2.2.2 with your production servers
And use this rule to detect rogue dhcp servers:
alert udp !$AUTHORIZED_DHCP 67 -> 255.255.255.255 any (msg: "Rogue DHCP Server OnNetwork"; sid:1000001;)
10)If you have tcpdump around, you can run and use this Bpf filter to detect rogue dhcp servers:
tcpdump -i eth0 -nn 'udp port 67 and !(host x.x.xx or host x.x.xx)'
11)And last, double check with your host-based firewall vendor that their product dose support NDIS-level firewalling. This means the FW will protect against unauthorized NDIS protocol registration by hooking NdisRegisterProtocol()/NdisOpenAdapter(). So, the FW will be notified when a NDIS protocol is trying to be registered or when it’s binding to some adapter.
Related Posts:







