DoS and DDoS attacks

 “I support freedom of expression, no matter whose, so I oppose DDoS attacks regardless of their target… they’re the poison gas of cyberspace.”
– John Perry Barlow

Definitions:

A Denial-of-Service (DoS) attack is a malicious attempt to disrupt the availability of a service or resource by overwhelming it with illegitimate traffic or requests, typically from a single source. In a classic DoS scenario, one host (or a single attacker) sends a flood of packets or exploits a vulnerability to exhaust the target’s network bandwidth, CPU, memory, or other resources, thereby denying service to legitimate users.

Distributed Denial-of-Service (DDoS) attack is essentially a large-scale DoS attack launched simultaneously from multiple compromised machines (hence “distributed”) to overwhelm the target. In a DDoS, an attacker typically controls a network of zombie hosts (a botnet) which collectively send traffic or requests to the victim, amplifying the attack power far beyond a single machine’s capacity.

Differences:

  1. Number of Attack Sources: A DoS attack comes from one host or a small group under one attacker’s control. A DDoS attack involves many distributed sources, often hundreds or thousands, acting together.
  2. Scale and Impact: DDoS attacks generate much more traffic than a DoS. They can overwhelm high-bandwidth connections and large server clusters.
  3. Attack Complexity: DDoS attacks often use several tactics at once. Attackers first infect devices with malware to build a botnet. Then they control these bots through command servers and launch a coordinated attack.
  4. Attribution and Evasion: DDoS traffic comes from many unrelated IPs. These are often spoofed or from infected devices like IoT gadgets and servers. This makes traceback hard. DoS attacks are easier to trace and block, though attackers may still spoof their IPs or use anonymity networks. Some DDoS attackers rent botnets through “booter” services.
  5. Mitigation Difficulty: A DoS attack may be stopped by blocking one IP. A DDoS attack is harder to stop. It requires advanced tools to filter traffic from many sources. These include DDoS protection systems, scrubbing centers, or content delivery networks. Smarter tools like traffic anomaly detection or challenge-response checks help separate attack traffic from real users.

Despite these differences, a DDoS is still a type of DoS. The goal is the same: to deny access to a service. DDoS attacks use many machines to boost traffic and make defense harder. Both rely on the imbalance in resource cost. It’s cheap for attackers to flood a system, but expensive for the target to manage the load.

Common DoS and DDoS Attacks:

Over the years, attackers have developed numerous tools to automate DoS and DDoS attacks. These range from simple single-host scripts to complex distributed botnet frameworks. Table 1 summarizes some well-known attacks, the typical OSI layer or protocol they target, and a brief description:

CategoryAttack NameDatasetsTarget Layer / ProtocolBrief Description
TCPTCP SYN FloodCICIDS2017, CSECICIDS2018, CICDDoS2019, EdgeIIoTsetL4 / TCPFloods server with SYN packets, exhausting connection queue.
Generic TCP FloodCICIDS2017, CSECICIDS2018, CICDDoS2019, BotIoTL4 / TCPHigh-rate TCP traffic (mixed flags) saturates server handling.
Teardrop (Fragment)KDD99, UNSWNB15, CSECICIDS2018L3 / IPOverlapping IP fragments disrupt packet reassembly.
UDPUDP FloodCICIDS2017, CSECICIDS2018, CICDDoS2019, EdgeIIoTsetL4 / UDPHigh-volume UDP packets overwhelm target with responses.
UDP-LagCICDDoS2019L4 / UDPSlow-rate packets keep resources engaged without detection.
NetBIOS FloodCICDDoS2019L4 / NetBIOS-NSSpoofed NetBIOS queries generate amplified traffic to victim.
Portmap AmplificationCICDDoS2019L7 / RPCExploits RPCbind to amplify traffic toward target.
SNMP AmplificationCICDDoS2019L7 / SNMPMassive SNMP replies reflect to victim using spoofed requests.
ICMPPing FloodUNSWNB15, CICIDS2017, CSECICIDS2018, CICDDoS2019, EdgeIIoTsetL3 / ICMPExcessive Echo Requests saturate target’s reply bandwidth.
Smurf AttackKDD99, CICDDoS2019, CSECICIDS2018L3 / ICMP (Broadcast)Broadcast ICMP with spoofed source reflects large reply sets.
Ping of DeathKDD99, CSECICIDS2018L3 / ICMPMalformed or oversized ICMP packets cause crashes.
HTTPHTTP GET/POST FloodCICIDS2017, CSECICIDS2018, EdgeIIoTsetL7 / HTTPMassive number of requests exhaust server-side threads.
WebDDoS (ARME)CICDDoS2019 (on the official website only, but not in the downloaded dataset)L7 / HTTPRandomized HTTP traffic evades caching and overloads servers.
Slowloris (Headers)UNSWNB15, CSECICIDS2018L7 / HTTPSlow headers keep HTTP connections open indefinitely.
Slow POST (R.U.D.Y.)CSECICIDS2018L7 / HTTPSlow POST bodies occupy server threads with long-lived connections.
Slow ReadUTSA-LowRate-DoS, CSECICIDS2018L7 / HTTPTiny advertised TCP windows stall server-side sending.
Slow HTTP TestCSECICIDS2018L7 / HTTPCombined slow attack types simulating realistic HTTP traffic.
DNS AmplificationCICDDoS2019, CSECICIDS2018L7 / DNSOpen resolvers reflect large responses to spoofed DNS queries.
HULK (HTTP Unbearable Load King)CSECICIDS2018L7 / HTTPHigh‑rate obfuscated HTTP GET flood that evades caching and hits direct server resources.
GoldenEyeCSECICIDS2018L7 / HTTPLayer‑7 HTTP flood using persistent connections (Keep‑Alive) to exhaust sockets.
OthersNTP AmplificationCICDDoS2019L7 / NTPSpoofed monlist or read requests yield large amplified replies.
SSDP AmplificationCICDDoS2019L7 / SSDPM-SEARCH queries trigger device responses reflected toward victim.
LDAP AmplificationCICDDoS2019, CSECICIDS2018L7 / LDAPSpoofed CLDAP requests return large directory responses to victim.
MSSQL AmplificationCICDDoS2019L7 / MSSQLSQL Resolution Service reflection yields large UDP responses.
TFTP AmplificationCICDDoS2019L7 / TFTPTFTP requests to misconfigured servers can generate amplified responses (~ 60×).