Man-in-the-middle attack

Template:TOC-right In a man-in-the-middle attack on a communications system, the attacker is the man-in-the-middle. He deceives the victims so they think they are communicating with each other but in fact both are talking to him. It is an active attack; the attacker needs not only the ability to intercept messages, but to insert his own and to prevent delivery of genuine ones. The principle is not used solely for conventional cryptographic countermeasures; a basic technique of deceptive electronic warfare is to transmit a "more plausible" signal (e.g., a radar return or a navigational code) than the real source.

Of course it need not be literally a man in the middle. The attacker might be a woman or a team, and the actual implementation of the attack is often along the lines of device-in-the-middle. The attacker either subverts an existing infrastructure device — a router, a security gateway (e.g., virtual private network (VPN) concentrator or application layer gateway machine, a firewall, an Asynchronous Transfer Mode (ATM) switch, ... — or inserts an extra device in the communication path to do the dirty work.

Conventionally, the communicating parties are A and B or Alice and Bob. Let us call the attacker Edward, for Eavesdropper or EvilDoer. Edward's goal is to trick both Alice and Bob into talking to him instead of each other. Alice's message go to Edward who reads them, perhaps alters them, and passes them on to Bob. Bob's replies also come to Edward, who passes them on to Alice.

If this attack succeeds, it is utterly devastating, completely destroying the security of the communication system. Consider General Alice ordering Major Bob to "Take Hill 37". Having Edward the Enemy able to read that order is highly undesirable. A successful man-in-the-middle attack allows that, but it also lets him do far worse. The man-in-the-middle can alter messages, so he can both send Bob some completely different orders and give General Alice bogus reports that appear to come from Bob. In essence, the Enemy completely controls the communication.

In a recent example in the US [1], attackers cyber-hijacked trucks. They got information on loads to be moved by hacking a government website, posed as a trucking company and submitted bids to the client then, posing as the client, arranged for a real trucking company to make the deliveries. They had made off wth nearly $500,000 before they were caught.

Principles of Countermeasures

Note that just encrypting the messages may not help. It does Alice absolutely no good to ensure that her messages are securely delivered and that only the recipient can read them if they are going to the wrong recipient. Along with any encryption, she needs some form of authentication to ensure she is in fact talking to Bob.

Encryption applied at lower levels of the communication system can prevent many man-in-the-middle attacks. For example, suppose we encrypt the communication link from Alice's headquarters to Bob's and Edward cannot break that encryption. He cannot then conduct a man-in-the-middle attack unless he can intercept messages inside one of the headquarters.

However, the most general defense against man-in-the-middle attacks is authentication. If Alice and Bob check that they are in fact talking to each other, then no man-in-the-middle attack can succeed unless the attacker can defeat whatever authentication mechanism is in play. For example, if Alice and Bob do a Diffie-Hellman key negotiation, they much each authenticate themselves to the other.

Trusted intermediaries and certificate authorities

If Alice and Bob both trust Charlie, and Charlie can independently verify identity, using a trusted channel to Alice (to verify Bob) and to Bob (to verify Alice), an alternative to Diffie-Hellman is use of a trusted intermediary.