DDoS Attack on GitHub - Revision history

Cskallak at 09:20, 22 May 2020

2020-05-22T09:20:20Z

← Older revision		Revision as of 09:20, 22 May 2020
Line 17:		Line 17:
	[3] https://www.wired.com/story/github-ddos-memcached/		[3] https://www.wired.com/story/github-ddos-memcached/

	[[Category:~~Documentation~~]]		[[Category:Basic]]

Cskallak: /* DDoS Attack */

2020-05-22T09:15:24Z

DDoS Attack

← Older revision		Revision as of 09:15, 22 May 2020
Line 3:		Line 3:
	[[File:Amplification DoS Attack.png\|thumb\|right\|400px\|\|Amplification DoS Attack]]		[[File:Amplification DoS Attack.png\|thumb\|right\|400px\|\|Amplification DoS Attack]]

	On February 28th, 2018 between 17:21 and 17:26 UTC GitHub got hit by the biggest DoS Attack recorded by that time. The Service was accessible from 17:26 to 17:30 UTC, due to the huge distributed denial-of-service attack (DDoS). The confidentiality and integrity of all data was preserved during the attack. The peak data throughput raised up to 1.35Tbps via 126.9 million packets per second [1].		On February 28th, 2018 between 17:21 and 17:26 UTC GitHub got hit by the biggest [https://wiki.elvis.science/index.php?title=Denial_of_Service_Attacks DoS Attack] recorded by that time. The Service was accessible from 17:26 to 17:30 UTC, due to the huge distributed denial-of-service attack (DDoS). The confidentiality and integrity of all data was preserved during the attack. The peak data throughput raised up to 1.35Tbps via 126.9 million packets per second [1].

	=== Background ===		=== Background ===

Cskallak: /* DDoS Attack */

2020-05-22T09:13:58Z

DDoS Attack

← Older revision		Revision as of 09:13, 22 May 2020
Line 1:		Line 1:
	== DDoS Attack ==		== DDoS Attack ==

			[[File:Amplification DoS Attack.png\|thumb\|right\|400px\|\|Amplification DoS Attack]]

	On February 28th, 2018 between 17:21 and 17:26 UTC GitHub got hit by the biggest DoS Attack recorded by that time. The Service was accessible from 17:26 to 17:30 UTC, due to the huge distributed denial-of-service attack (DDoS). The confidentiality and integrity of all data was preserved during the attack. The peak data throughput raised up to 1.35Tbps via 126.9 million packets per second [1].		On February 28th, 2018 between 17:21 and 17:26 UTC GitHub got hit by the biggest DoS Attack recorded by that time. The Service was accessible from 17:26 to 17:30 UTC, due to the huge distributed denial-of-service attack (DDoS). The confidentiality and integrity of all data was preserved during the attack. The peak data throughput raised up to 1.35Tbps via 126.9 million packets per second [1].

Cskallak: /* References */

2020-05-22T09:12:58Z

References

← Older revision		Revision as of 09:12, 22 May 2020
Line 10:		Line 10:

	[1] https://github.blog/2018-03-01-ddos-incident-report/		[1] https://github.blog/2018-03-01-ddos-incident-report/

	[2] https://blog.cloudflare.com/memcrashed-major-amplification-attacks-from-port-11211/		[2] https://blog.cloudflare.com/memcrashed-major-amplification-attacks-from-port-11211/

	[3] https://www.wired.com/story/github-ddos-memcached/		[3] https://www.wired.com/story/github-ddos-memcached/

	[[Category:Documentation]]		[[Category:Documentation]]

Cskallak: /* Background */

2020-05-22T09:12:41Z

Background

← Older revision		Revision as of 09:12, 22 May 2020
Line 3:		Line 3:
	On February 28th, 2018 between 17:21 and 17:26 UTC GitHub got hit by the biggest DoS Attack recorded by that time. The Service was accessible from 17:26 to 17:30 UTC, due to the huge distributed denial-of-service attack (DDoS). The confidentiality and integrity of all data was preserved during the attack. The peak data throughput raised up to 1.35Tbps via 126.9 million packets per second [1].		On February 28th, 2018 between 17:21 and 17:26 UTC GitHub got hit by the biggest DoS Attack recorded by that time. The Service was accessible from 17:26 to 17:30 UTC, due to the huge distributed denial-of-service attack (DDoS). The confidentiality and integrity of all data was preserved during the attack. The peak data throughput raised up to 1.35Tbps via 126.9 million packets per second [1].

	== Background ==		=== Background ===

	The attackers used a distributed amplification DoS attack to gain a amplify the attack throughput. They used the Memcached protocol which relies on UDP, which doesn’t check the integrity of the IP header. This allowed the attackers to spoof the source IP address with the victims IP. Memcached server response with an up to 750kB big response message to an 15byte request. This is and amplification factor of 51,200 [2].		The attackers used a distributed amplification DoS attack to gain a amplify the attack throughput. They used the Memcached protocol which relies on UDP, which doesn’t check the integrity of the IP header. This allowed the attackers to spoof the source IP address with the victims IP. Memcached server response with an up to 750kB big response message to an 15byte request. This is and amplification factor of 51,200 [2].

Cskallak: Created page with "== DDoS Attack == On February 28th, 2018 between 17:21 and 17:26 UTC GitHub got hit by the biggest DoS Attack recorded by that time. The Service was accessible from 17:26 to..."

2020-05-22T09:12:26Z

Created page with "== DDoS Attack == On February 28th, 2018 between 17:21 and 17:26 UTC GitHub got hit by the biggest DoS Attack recorded by that time. The Service was accessible from 17:26 to..."

New page

== DDoS Attack ==

On February 28th, 2018 between 17:21 and 17:26 UTC GitHub got hit by the biggest DoS Attack recorded by that time. The Service was accessible from 17:26 to 17:30 UTC, due to the huge distributed denial-of-service attack (DDoS). The confidentiality and integrity of all data was preserved during the attack. The peak data throughput raised up to 1.35Tbps via 126.9 million packets per second [1].

== Background ==

The attackers used a distributed amplification DoS attack to gain a amplify the attack throughput. They used the Memcached protocol which relies on UDP, which doesn’t check the integrity of the IP header. This allowed the attackers to spoof the source IP address with the victims IP. Memcached server response with an up to 750kB big response message to an 15byte request. This is and amplification factor of 51,200 [2].

== References ==

[1] https://github.blog/2018-03-01-ddos-incident-report/
[2] https://blog.cloudflare.com/memcrashed-major-amplification-attacks-from-port-11211/
[3] https://www.wired.com/story/github-ddos-memcached/

[[Category:Documentation]]