ARP spoofing
What is ARP spoofing?
ARP spoofing (ARP poisoning) is an attack on a local IPv4 network where a device sends forged ARP replies claiming to own an IP address belonging to another host, such as the router, letting it intercept or redirect traffic -- a classic man-in-the-middle setup. AdminKit's subnet calculator shows which devices share the broadcast domain this attack depends on.
By AdminKit team, Netbase JSC · Updated
ARP spoofing (also called ARP poisoning) is an attack on a local IPv4 network where a device sends forged Address Resolution Protocol (defined in RFC 826, also tracked on the IETF Datatracker) replies, claiming to own an IP address that actually belongs to another host, such as the router. Because ARP has no built-in authentication, other devices on the same subnet update their ARP tables to trust the forged mapping, which lets the attacker intercept, modify, or drop traffic meant for someone else — a classic man-in-the-middle setup CISA catalogs as ARP cache poisoning. MITRE ATT&CK’s ARP Cache Poisoning entry adds that an attacker need not wait for a request at all: a gratuitous ARP reply can announce ownership of an IP address to every device on the local segment. It only works within a single broadcast domain (the attacker must already be on the same LAN or Wi-Fi network), which limits it to insider threats, compromised devices, or open/shared networks. Switches with dynamic ARP inspection, static ARP entries for critical hosts, and network segmentation are the standard mitigations; IPv6 networks use Neighbor Discovery Protocol instead, which has its own, different spoofing risks. BCP 38 ingress filtering, defined in RFC 2827, targets a different layer of forgery — a spoofed IP source address — rather than this local link-layer trick.
ARP spoofing is part of AdminKit’s IP & network cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
Why does ARP spoofing work?
Because ARP has no built-in authentication, so other devices on the same subnet accept a forged ARP reply and update their ARP tables to trust it, even though it was never requested.
Can ARP spoofing be launched from outside the local network?
No -- it only works within a single broadcast domain, since the attacker must already be on the same LAN or Wi-Fi network as the victim.
What are the standard mitigations against ARP spoofing?
Switches with dynamic ARP inspection, static ARP entries for critical hosts, and network segmentation are the standard mitigations.
Is ARP spoofing a risk on IPv6 networks?
Not directly -- IPv6 uses Neighbor Discovery Protocol instead of ARP, which has its own, different spoofing risks rather than inheriting ARP's.
Sources
- RFC 826 -- An Ethernet Address Resolution Protocol
- RFC 2827 -- Network Ingress Filtering (BCP 38)
- IETF Datatracker -- RFC 826 (Address Resolution Protocol) document status
- CISA -- ARP Cache Poisoning (T1557.002), Eviction Strategies Tool
- Adversary-in-the-Middle: ARP Cache Poisoning, Sub-technique T1557.002 | MITRE ATT&CK