ARP spoofing

(Redirected from Arp poisoning)

In computer networking, ARP spoofing (also ARP cache poisoning or ARP poison routing) is a technique by which an attacker sends (spoofed) Address Resolution Protocol (ARP) messages onto a local area network. Generally, the aim is to associate the attacker's MAC address with the IP address of another host, such as the default gateway, causing any traffic meant for that IP address to be sent to the attacker instead.

A successful ARP spoofing (poisoning) attack allows an attacker to alter routing on a network, effectively allowing for a man-in-the-middle attack.

ARP spoofing may allow an attacker to intercept data frames on a network, modify the traffic, or stop all traffic. Often the attack is used as an opening for other attacks, such as denial of service, man in the middle, or session hijacking attacks.[1]

The attack can only be used on networks that use ARP, and requires that the attacker has direct access to the local network segment to be attacked.[2]

ARP vulnerabilities

edit

The Address Resolution Protocol (ARP) is a widely used communications protocol for resolving Internet layer addresses into link layer addresses.

When an Internet Protocol (IP) datagram is sent from one host to another in a local area network, the destination IP address must be resolved to a MAC address for transmission via the data link layer. When another host's IP address is known, and its MAC address is needed, a broadcast packet is sent out on the local network. This packet is known as an ARP request. The destination machine with the IP in the ARP request then responds with an ARP reply that contains the MAC address for that IP.[2]

ARP is a stateless protocol. Network hosts will automatically cache any ARP replies they receive, regardless of whether network hosts requested them. Even ARP entries that have not yet expired will be overwritten when a new ARP reply packet is received. There is no method in the ARP protocol by which a host can authenticate the peer from which the packet originated. This behavior is the vulnerability that allows ARP spoofing to occur.[1][2][3]

Attack anatomy

edit

The basic principle behind ARP spoofing is to exploit the lack of authentication in the ARP protocol by sending spoofed ARP messages onto the LAN. ARP spoofing attacks can be run from a compromised host on the LAN, or from an attacker's machine that is connected directly to the target LAN.

An attacker using ARP spoofing will disguise as a host to the transmission of data on the network between the users.[4] Then users would not know that the attacker is not the real host on the network.[4]

Generally, the goal of the attack is to associate the attacker's host MAC address with the IP address of a target host, so that any traffic meant for the target host will be sent to the attacker's host. The attacker may choose to inspect the packets (spying), while forwarding the traffic to the actual default destination to avoid discovery, modify the data before forwarding it (man-in-the-middle attack), or launch a denial-of-service attack by causing some or all of the packets on the network to be dropped.

Defenses

edit

Static ARP entries

edit

The simplest form of certification is the use of static, read-only entries for critical services in the ARP cache of a host. IP address-to-MAC address mappings in the local ARP cache may be statically entered. Hosts don't need to transmit ARP requests where such entries exist.[5] While static entries provide some security against spoofing, they result in maintenance efforts as address mappings for all systems in the network must be generated and distributed. This does not scale on a large network since the mapping has to be set for each pair of machines resulting in n2-n ARP entries that have to be configured when n machines are present; On each machine there must be an ARP entry for every other machine on the network; n-1 ARP entries on each of the n machines.

Detection and prevention software

edit

Software that detects ARP spoofing generally relies on some form of certification or cross-checking of ARP responses. Uncertified ARP responses are then blocked. These techniques may be integrated with the DHCP server so that both dynamic and static IP addresses are certified. This capability may be implemented in individual hosts or may be integrated into Ethernet switches or other network equipment. The existence of multiple IP addresses associated with a single MAC address may indicate an ARP spoof attack, although there are legitimate uses of such a configuration. In a more passive approach, a device listens for ARP replies on a network, and sends a notification via email when an ARP entry changes.[6]

AntiARP[7] also provides Windows-based spoofing prevention at the kernel level. ArpStar is a Linux module for kernel 2.6 and Linksys routers that drops invalid packets that violate mapping, and contains an option to repoison or heal.

Some virtualized environments such as KVM also provide security mechanisms to prevent MAC spoofing between guests running on the same host.[8]

Additionally some Ethernet adapters provide MAC and VLAN anti-spoofing features.[9]

OpenBSD watches passively for hosts impersonating the local host and notifies in case of any attempt to overwrite a permanent entry.[10]

OS security

edit

Operating systems react differently. Linux ignores unsolicited replies, but, on the other hand, uses responses to requests from other machines to update its cache. Solaris accepts updates on entries only after a timeout. In Microsoft Windows, the behavior of the ARP cache can be configured through several registry entries under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters, ArpCacheLife, ArpCacheMinReferenceLife, ArpUseEtherSNAP, ArpTRSingleRoute, ArpAlwaysSourceRoute, ArpRetryCount.[11]

Legitimate usage

edit

The techniques that are used in ARP spoofing can also be used to implement redundancy of network services. For example, some software allows a backup server to issue a gratuitous ARP request in order to take over for a defective server and transparently offer redundancy.[12][13] Circle[14] and CUJO are two companies that have commercialized products centered around this strategy.

ARP spoofing is often used by developers to debug IP traffic between two hosts when a switch is in use: if host A and host B are communicating through an Ethernet switch, their traffic would normally be invisible to a third monitoring host M. The developer configures A to have M's MAC address for B, and B to have M's MAC address for A; and also configures M to forward packets. M can now monitor the traffic, exactly as in a man-in-the-middle attack.

Tools

edit

Defense

edit
Name OS GUI Free Protection Per interface Active/passive Notes
Agnitum Outpost Firewall Windows Yes No Yes No passive
AntiARP Windows Yes No Yes No active+passive
Antidote[15] Linux No Yes No ? passive Linux daemon, monitors mappings, unusually large number of ARP packets.
Arp_Antidote[16] Linux No Yes No ? passive Linux Kernel Patch for 2.4.18 – 2.4.20, watches mappings, can define action to take when.
Arpalert Linux No Yes No Yes passive Predefined list of allowed MAC addresses, alert if MAC that is not in list.
ArpON Linux No Yes Yes Yes active+passive Portable handler daemon for securing ARP against spoofing, cache poisoning or poison routing attacks in static, dynamic and hybrid networks.
ArpGuard Mac Yes No Yes Yes active+passive
ArpStar Linux No Yes Yes ? passive
Arpwatch Linux No Yes No Yes passive Keep mappings of IP-MAC pairs, report changes via Syslog, Email.
ArpwatchNG Linux No Yes No No passive Keep mappings of IP-MAC pairs, report changes via Syslog, Email.
Colasoft Capsa Windows Yes No No Yes no detection, only analysis with manual inspection
cSploit[17] Android (rooted only) Yes Yes No Yes passive
elmoCut[18] Windows Yes Yes No ? passive EyeCandy ARP spoofer for Windows
Prelude IDS ? ? ? ? ? ? ArpSpoof plugin, basic checks on addresses.
Panda Security Windows ? ? Yes ? Active Performs basic checks on addresses
remarp Linux No Yes No No passive
Snort Windows/Linux No Yes No Yes passive Snort preprocessor Arpspoof, performs basic checks on addresses
Winarpwatch Windows No Yes No No passive Keep mappings of IP-MAC pairs, report changes via Syslog, Email.
XArp[19] Windows, Linux Yes Yes (+pro version) Yes (Linux, pro) Yes active + passive Advanced ARP spoofing detection, active probing and passive checks. Two user interfaces: normal view with predefined security levels, pro view with per-interface configuration of detection modules and active validation. Windows and Linux, GUI-based.
Seconfig XP Windows 2000/XP/2003 only Yes Yes Yes No only activates protection built-in some versions of Windows
zANTI Android (rooted only) Yes Yes No ? passive
NetSec Framework Linux No Yes No No active
anti-arpspoof[20] Windows Yes Yes ? ? ?
DefendARP:[21] ? ? ? ? ? ? A host-based ARP table monitoring and defense tool designed for use when connecting to public wifi. DefendARP detects ARP poisoning attacks, corrects the poisoned entry, and identifies the MAC and IP address of the attacker.
NetCutDefender:[22] Windows ? ? ? ? ? GUI for Windows that can protect from ARP attacks

Spoofing

edit

Some of the tools that can be used to carry out ARP spoofing attacks:

See also

edit

References

edit
  1. ^ a b Ramachandran, Vivek & Nandi, Sukumar (2005). "Detecting ARP Spoofing: An Active Technique". In Jajodia, Suchil & Mazumdar, Chandan (eds.). Information systems security: first international conference, ICISS 2005, Kolkata, India, December 19–21, 2005 : proceedings. Birkhauser. p. 239. ISBN 978-3-540-30706-8.
  2. ^ a b c Lockhart, Andrew (2007). Network security hacks. O'Reilly. p. 184. ISBN 978-0-596-52763-1.
  3. ^ Steve Gibson (2005-12-11). "ARP Cache Poisoning". GRC.
  4. ^ a b Moon, Daesung; Lee, Jae Dong; Jeong, Young-Sik; Park, Jong Hyuk (2014-12-19). "RTNSS: a routing trace-based network security system for preventing ARP spoofing attacks". The Journal of Supercomputing. 72 (5): 1740–1756. doi:10.1007/s11227-014-1353-0. ISSN 0920-8542. S2CID 18861134. Archived from the original on 2021-01-23. Retrieved 2021-01-23.
  5. ^ Lockhart, Andrew (2007). Network security hacks. O'Reilly. p. 186. ISBN 978-0-596-52763-1.
  6. ^ "A Security Approach to Prevent ARP Poisoning and Defensive tools". ResearchGate. Archived from the original on 2019-05-03. Retrieved 2019-03-22.
  7. ^ AntiARP Archived June 6, 2011, at the Wayback Machine
  8. ^ "Daniel P. Berrangé » Blog Archive » Guest MAC spoofing denial of service and preventing it with libvirt and KVM". Archived from the original on 2019-08-09. Retrieved 2019-08-09.
  9. ^ "Archived copy". Archived from the original on 2019-09-03. Retrieved 2019-08-09.{{cite web}}: CS1 maint: archived copy as title (link)
  10. ^ "Arp(4) - OpenBSD manual pages". Archived from the original on 2019-08-09. Retrieved 2019-08-09.
  11. ^ "Address Resolution Protocol". 18 July 2012. Archived from the original on 2021-01-23. Retrieved 2017-08-26.
  12. ^ "OpenBSD manpage for CARP (4)". Archived from the original on 2018-02-05. Retrieved 2018-02-04., retrieved 2018-02-04
  13. ^ Simon Horman. "Ultra Monkey: IP Address Takeover". Archived from the original on 2012-11-18. Retrieved 2013-01-04., retrieved 2013-01-04
  14. ^ Barrett, Brian. "Circle with Disney Locks Down Kids Devices from Afar". Wired. Archived from the original on 2016-10-12. Retrieved 2016-10-12., retrieved 2016-10-12
  15. ^ "Antidote". Archived from the original on 2012-03-13. Retrieved 2014-04-07.
  16. ^ "Arp_Antidote". Archived from the original on 2012-01-14. Retrieved 2011-08-02.
  17. ^ "cSploit". tux_mind. Archived from the original on 2019-03-12. Retrieved 2015-10-17.
  18. ^ "elmoCut: EyeCandy ARP Spoofer (GitHub Home Page)". GitHub.
  19. ^ "XArp". Archived from the original on 2020-06-16. Retrieved 2021-01-23.
  20. ^ anti-arpspoof Archived August 31, 2008, at the Wayback Machine
  21. ^ "Defense Scripts | ARP Poisoning". Archived from the original on 2013-01-22. Retrieved 2013-06-08.
  22. ^ "Netcut defender | Arcai.com". Archived from the original on 2019-04-08. Retrieved 2018-02-07.
  23. ^ "ARP Vulnerabilities: The Complete Documentation". l0T3K. Archived from the original on 2011-03-05. Retrieved 2011-05-03.
edit