Re:Technical Details Behind a 400Gbps NTP Amplification DDoS...
by alex1 on Thursday February 13, 2014 @09:22AM
(#7231493)
FWIW, here's what I got on an Ubuntu 12.04.3 server running on my LAN. It looks like we should be fine with the defaults on Ubuntu at least. (Obviously always a good idea to use ufw/iptables to block everything you don't need exposed so you don't have to worry about stuff like this).
Before installing ntp (from another host on my LAN):
$ ntpdc -n -c monlist 192.168.1.50
ntpdc: read: Connection refused
After installing ntp (from another host on my LAN): $ ntpdc -n -c monlist 192.168.1.50
192.168.1.50: timed out, nothing received
***Request timed out
After installing ntp (from the server itself): $ ntpdc -n -c monlist localhost
remote address port local address count m ver rstr avgint lstint
===============================================================================
91.189.94.4 123 192.168.1.50 1 4 4 1d0 54 54
...
Re:Technical Details Behind a 400Gbps NTP Amplification DDoS...
by voltagex_ on Thursday February 13, 2014 @02:59PM
(#7233850)
Thanks, I should have checked this.
Re:Technical Details Behind a 400Gbps NTP Amplification DDoS...
by devicenull on Thursday February 13, 2014 @09:15AM
(#7231459)
Debian's something I checked when I first started seeing this, and their default config is not vulnerable.
Being able tod this via localhost is not a problem, it's when it's open to the internet.
Re:Technical Details Behind a 400Gbps NTP Amplification DDoS...
by shawabawa3 on Thursday February 13, 2014 @09:12AM
(#7231434)
Just tried it on my server. Works for localhost but times out remotely
FWIW, if you install the ntp package and do ntpdc -n -c monlist localhost you'll get a response but I haven't checked if it's configured by default to reject non-LAN requests.