CyberKit

Network ports

Port 67/udp: DHCP Server (BOOTPS)

Category: Network Infrastructure. Range: well-known. Status: iana registered.

What runs here

The port a DHCP (Dynamic Host Configuration Protocol) server listens on for client requests, inherited from the older BOOTP protocol it extends (the IANA service name is still 'bootps'). The server uses it to receive DISCOVER/REQUEST broadcasts and hand out IP leases plus configuration options (gateway, DNS, and (for network-boot setups), a TFTP server address).

Why it matters

DHCP has no built-in authentication, so any host on the local broadcast segment can pose as a server: a rogue DHCP server can hand out a malicious default gateway or DNS server to every client that asks, silently putting the attacker in the middle of victims' traffic. It's also one of the oldest, most reliable ways to pivot from a compromised or physically-accessible network segment into broad, low-effort visibility over other hosts on that segment.

Where you see it

Legitimately: exactly one authorized DHCP server (or a small, known set in a failover/HA configuration) answering client leases on a subnet. Anomalously/maliciously: a second, unauthorized host answering DHCP DISCOVER broadcasts (a rogue DHCP server), or a flood of DISCOVER messages from spoofed MAC addresses intended to exhaust the legitimate server's address pool.

What to look for

Indicators
SignalWhat it means
Unexpected DHCP server sourceA DHCP OFFER/ACK from a MAC/IP outside the known, authorized server list is the direct signature of a rogue DHCP server / man-in-the-middle setup and should be investigated immediately.
Pool exhaustion / high lease churnAn unusually high rate of new DISCOVER requests exhausting the address pool can indicate a DHCP starvation attack, often a precursor to standing up a rogue server once clients fail over to it.

Related ports

  • 68/udp: DHCP Client (BOOTPC)
  • 69/udp: TFTP (Trivial File Transfer Protocol)

ATT&CK techniques

Sources