- The configuration token method is vulnerable to interception, and
- The delayed authentication mechanism is vulnerable to DDoS floods.
For example, DHCP_Gobbler is a proof of concept tool that attacks RFC 3118 by grabbing all available DHCP addresses,...
preventing allocation to legitimate new machines.
To learn more about DHCP improvements related to security and more, visit the IETF's DHC working group page -- for example, see Internet Drafts regarding DHCP authentication with IPv6 and DHCP Relay.
Note that DHCP can be used by any kind of IP network, including wireless LANs. Wireless LANs are inherently more vulnerable to interception and flooding than privately-operated Ethernet LANs. Link encryption (WPA/WPA2) can be used to prevent DHCP request interception on a wireless LAN. Preventing flooding is trickier, since you can't really prevent wireless stations from transmitting. However, you CAN stop transmitted packets from reaching your DHCP server -- for example, by using 802.1X port access control.
Related Q&A from Lisa Phifer
The enterprise mobility management market for wearable devices is in its infancy, but IT can still use existing EMM tools to manage wearables.continue reading
Wireless expert Lisa A. Phifer explains to what extent WEP cracking remains a worrisome issue. It all depends on your company's WLAN security policy.continue reading
Wireless expert Lisa A. Phifer explains why you shouldn't stop using 802.1X authentication methods for enterprise WLAN access control.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.