"Operation Blackout" to target DNS root server infrastructure

Recently, an article was posted on the pastebin site claiming to be from “anonymous”, the notorious hacking group, in which they outlined a proposal to attack the DNS root server infrastructure that underpins the Internet. They effectively want to turn the Internet “off” on 31st March 2012 by preventing the ability of the DNS root servers to respond to legitimate queries, thus leading users to experience timeouts when trying to reach their favourite web sites (of course the attack could also impact many other Internet services such as email).

The article proposes to use a “reflective amplification attack” in order to launch a denial of service attack against the 13 root server IP addresses. This type of attack is not particularly clever and is very simple to invoke, provided you have control of enough clients. Anonymous probably do have access to huge botnets which could be used to launch this type of attack. Basically the botnet clients would launch a huge number of small queries for DNS records that invoke a large response packet (for instance, you could look up the DNSSEC records for one of the TLD’s or even the root itself – the response that comes back is much larger than the original query, hence the traffic is “amplified”). But in order to direct the amplified traffic back to the root servers, the source IP address of each query is spoofed, so that the response goes to one of the root server IP addresses rather than the botnet client.

The root server infrastructure has been the target of various attacks over the years, but an increasingly resilient infrastructure has been built based upon “anycast” technology. So while there are only 13 public IP addresses used to advertise the root servers, there are in fact 259 physical servers operating behind these IP addresses. It is the Internet’s routing protocols that determine which DNS server you actually reach, so trying to target a specific physical server in order to launch a DDoS attack against it would actually be quite difficult.

So if this proposal is genuine, we could see the root server infrastructure come under sustained attack for a period of time, but whether the attack has any serious impact will be down to the distribution of botnet clients and the routing topology between them and the physical root servers. In fact I would imagine that some servers will be impacted, but the root infrastructure as a whole should survive. With the caching mechanism built into recursive DNS servers, end-users may not even notice if some of the root infrastructure is taken down.

It will be very interesting to see how effective the root server anycast deployment is at mitigating this attack.

Here’s the proposal in its entirety:

  1. ———————————————————————–
  2. 01001111 01110000 01100101 01110010 01100001 01110100 01101001 01101111
  3. 01101110  01000111 01101100 01101111 01100010 01100001 01101100
  4. 01000010 01101100 01100001 01100011 01101011 01101111 01110101 01110100
  5. ———————————————————————–
  6.   ___                     _   _             ___ _     _          _
  7. / _ \ _ __  ___ _ _ __ _| |_(_)___ _ _    / __| |___| |__  __ _| |
  8. | (_) | ‘_ \/ -_) ‘_/ _` |  _| / _ \ ‘ \  | (_ | / _ \ ‘_ \/ _` | |
  9. \___/| .__/\___|_| \__,_|\__|_\___/_||_|  \___|_\___/_.__/\__,_|_|
  10.       |_|                                                         
  11. ___ _         _            _  
  12. | _ ) |__ _ __| |_____ _  _| |_
  13. | _ \ / _` / _| / / _ \ || |  _|
  14. |___/_\__,_\__|_\_\___/\_,_|\__|
  16. ———————————————————————–
  17. 01001111 01110000 01100101 01110010 01100001 01110100 01101001 01101111
  18. 01101110  01000111 01101100 01101111 01100010 01100001 01101100
  19. 01000010 01101100 01100001 01100011 01101011 01101111 01110101 01110100
  20. ———————————————————————–
  21.                 “The greatest enemy of freedom is a happy slave.”
  23. To protest SOPA, Wallstreet, our irresponsible leaders and the beloved
  24. bankers who are starving the world for their own selfish needs out of
  25. sheer sadistic fun, On March 31, the Internet will go Black.
  27. In order to shut the Internet down, one thing is to be done. Down the
  28. 13 root DNS servers of the Internet. Those servers are as follow:
  30. A
  31. B
  32. C
  33. D
  34. E
  35. F
  36. G
  37. H
  38. I
  39. J
  40. K
  41. L
  42. M
  44. By cutting these off the Internet, nobody will be able to perform a
  45. domain name lookup, thus, disabling the HTTP Internet, which is,
  46. after all, the most widely used function of the Web. Anybody entering
  47. http://www.google.com” or ANY other url, will get an error page,
  48. thus, they will think the Internet is down, which is, close enough.
  49. Remember, this is a protest, we are not trying to ‘kill’ the Internet,
  50. we are only temporarily shutting it down where it hurts the most.
  52. While some ISPs uses DNS caching, most are configured to use a low
  53. expire time for the cache, thus not being a valid failover solution
  54. in the case the root servers are down. It is mostly used for speed,
  55. not redundancy.
  57. I have compiled a Reflective DNS Amplification DDoS tool to be used for
  58. this attack. It is based on AntiSec’s DHN, contains a few bugfix, a
  59. different dns list/target support and is a bit stripped down for speed.
  61. The principle is simple; a flaw that uses forged UDP packets is to be
  62. used to trigger a rush of DNS queries all redirected and reflected to
  63. those 13 IPs. The flaw is as follow; since the UDP protocol allows it,
  64. we can change the source IP of the sender to our target, thus spoofing
  65. the source of the DNS query.
  67. The DNS server will then respond to that query by sending the answer to
  68. the spoofed IP. Since the answer is always bigger than the query, the
  69. DNS answers will then flood the target ip. It is called an amplified
  70. because we can use small packets to generate large traffic. It is called
  71. reflective because we will not send the queries to the root name servers,
  72. instead, we will use a list of known vulnerable DNS servers which will
  73. attack the root servers for us.
  75. DDoS request —>       [Vulnerable DNS Server  ]       <—> Normal answer     <—>   Normal Client request
  76.                                                         \
  77.                                                          | ( Spoofed UDP requests
  78.                                                          |   will redirect the answers
  79.                                                          |   to the root name server )
  80.                                                          |
  81.                                         [       13 root servers         ] * BAM
  83. Since the attack will be using static IP addresses, it will not rely
  84. on name server resolution, thus enabling us to keep the attack up even
  85. while the Internet is down. The very fact that nobody will be able to
  86. make new requests to use the Internet will slow down those who will try
  87. to stop the attack.
  89.         “He who sacrifices freedom for security deserves neither.”
  90.                                                                 Benjamin Franklin
  92. We know you wont’ listen. We know you won’t change. We know it’s because
  93. you don’t want to. We know it’s because you like it how it is. You bullied
  94. us into your delusion. We have seen you brutalize harmless old womans who were
  95. protesting for peace. We do not forget because we know you will only use that
  96. to start again. We know your true face. We know you will never stop. Neither
  97. are we. We know.
  99. We are Anonymous.
  100. We are Legion.
  101. We do not Forgive.
  102. We do not Forget.
  103. You know who you are, Expect us.
This entry was posted in Computers and Internet. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s