SYN flood

Denial-of-service attack

A normal connection between a user (Alice) and a server. The three-way handshake is correctly performed. SYN Flood. The attacker (Mallory, green) sends several packets but does not send the "ACK" back to the server. The connections are hence half-opened and consuming server resources. Legitimate user Alice (purple) tries to connect, but the server refuses to open a connection, a denial of service.

A SYN flood is a form of denial-of-service attack on data communications in which an attacker rapidly initiates a connection to a server without finalizing the connection. The server has to spend resources waiting for half-opened connections, which can consume enough resources to make the system unresponsive to legitimate traffic.[1][2]

The packet that the attacker sends is the `SYN` packet, a part of TCP's three-way handshake used to establish a connection.[3]

## Technical details[edit]

When a client attempts to start a TCP connection to a server, the client and server exchange a series of messages which normally runs like this:

1. The client requests a connection by sending a `SYN` (synchronize) message to the server.
2. The server acknowledges this request by sending `SYN-ACK` back to the client.
3. The client responds with an `ACK`, and the connection is established.

This is called the TCP three-way handshake, and is the foundation for every connection established using the TCP protocol.

A SYN flood attack works by not responding to the server with the expected `ACK` code. The malicious client can either simply not send the expected `ACK`, or by spoofing the source IP address in the `SYN`, cause the server to send the `SYN-ACK` to a falsified IP address – which will not send an `ACK` because it "knows" that it never sent a `SYN`.

The server will wait for the acknowledgement for some time, as simple network congestion could also be the cause of the missing `ACK`. However, in an attack, the half-open connections created by the malicious client bind resources on the server and may eventually exceed the resources available on the server. At that point, the server cannot connect to any clients, whether legitimate or otherwise. This effectively denies service to legitimate clients. Some systems may also malfunction or crash when other operating system functions are starved of resources in this way.

## Countermeasures[edit]

There are a number of well-known countermeasures listed in RFC 4987 including:

1. Filtering
2. Increasing backlog
3. Reducing SYN-RECEIVED timer
4. Recycling the oldest half-open TCP
5. SYN cache
6. SYN cookies
7. Hybrid approaches
8. Firewalls and proxies

## See also[edit]

* Fraggle attack
* Internet Control Message Protocol
* IP address spoofing
* Ping flood
* Smurf attack
* UDP flood attack

## References[edit]

1. ^ "CERT Advisory CA-1996-21 TCP SYN Flooding and IP Spoofing Attacks" (PDF). Carnegie Mellon University Software Engineering Institute. Archived from the original on 2000-12-14. Retrieved 18 September 2019.
2. ^ New York's Panix Service Is Crippled by Hacker Attack, New York Times, September 14, 1996
3. ^ "What is a DDoS Attack?". Cloudflare.com. Cloudflare. Retrieved 4 May 2020.

## External links[edit]

* Official CERT advisory on SYN Attacks