07.03.2012, 00:47
This is the second time our server was attacking an other IP with the means of UDP floods. Very annoying due to the fact the datacenter's security systems notice the attacks and disable the host...
To be clear, our samp server was the SOURCE of the attack... No other application was running (and technically can't occupy the same port that is already in use by the samp server itself), no signs of intrusions were found in the host logs and no scripts (typically php or pl scripts for udp floods) were found either.
The only conlusion is that the samp server is used to perfom attacks on others somehow.
If you see the logs of the attack, it's as if the samp server is trying to find an available port with the client, which might look like a normal client connection attempt. This happens a few times per second for quite a while, see how the port on the client side is changing:
startime endtime
scr: port dst: port
-----------------------------------------------------------
-----------------------------------
2012-02-01 09:17:07 2012-02-01 09:17:07
9*.2*.6*.5*:7777 17*.6*.13*.15*:58421
2012-02-01 09:17:07 2012-02-01 09:17:07
9*.2*.6*.5*:7777 17*.6*.13*.15*:24395
2012-02-01 09:17:07 2012-02-01 09:17:07
9*.2*.6*.5*:7777 17*.6*.13*.15*:9050
2012-02-01 09:17:07 2012-02-01 09:17:07
9*.2*.6*.5*:7777 17*.6*.13*.15*:59222
2012-02-01 09:17:07 2012-02-01 09:17:07
9*.2*.6*.5*:7777 17*.6*.13*.15*:39286
2012-02-01 09:17:07 2012-02-01 09:17:07
9*.2*.6*.5*:7777 17*.6*.13*.15*:48431
2012-02-01 09:17:07 2012-02-01 09:17:07
... and so on
second time it attacks a few ips in the same range:
06:07:33.829922 IP 9*.2*.6*.5*:7777 > **.2*8.67.97.28974:
UDP, length 14
06:07:33.829922 IP 9*.2*.6*.5*:7777 > **.2*8.67.98.28990:
UDP, length 14
06:07:33.837922 IP 9*.2*.6*.5*:7777 > **.2*8.67.96.28971:
UDP, length 14
06:07:33.841921 IP 9*.2*.6*.5*:7777 > **.2*8.67.98.28990:
UDP, length 14
06:07:33.841921 IP 9*.2*.6*.5*:7777 > **.2*8.67.97.28974:
UDP, length 14
... and so on
(ips partially censored)
The port of the source (7777) is our samp server...
Server version is Linux.
Outgoing traffic exceeded 300mbit.
The outgoing connection attempts (e.g the udp floods) do not show in the samp log file.
It, obviously, lags the sh*t out of the players, causing timeouts.
is this a known issue and fixable?
i suppose this could be a serious security gab in the server software... once this "tool" or "technique" is out there it can be very damaging for many samp servers and/or communities...
To be clear, our samp server was the SOURCE of the attack... No other application was running (and technically can't occupy the same port that is already in use by the samp server itself), no signs of intrusions were found in the host logs and no scripts (typically php or pl scripts for udp floods) were found either.
The only conlusion is that the samp server is used to perfom attacks on others somehow.
If you see the logs of the attack, it's as if the samp server is trying to find an available port with the client, which might look like a normal client connection attempt. This happens a few times per second for quite a while, see how the port on the client side is changing:
startime endtime
scr: port dst: port
-----------------------------------------------------------
-----------------------------------
2012-02-01 09:17:07 2012-02-01 09:17:07
9*.2*.6*.5*:7777 17*.6*.13*.15*:58421
2012-02-01 09:17:07 2012-02-01 09:17:07
9*.2*.6*.5*:7777 17*.6*.13*.15*:24395
2012-02-01 09:17:07 2012-02-01 09:17:07
9*.2*.6*.5*:7777 17*.6*.13*.15*:9050
2012-02-01 09:17:07 2012-02-01 09:17:07
9*.2*.6*.5*:7777 17*.6*.13*.15*:59222
2012-02-01 09:17:07 2012-02-01 09:17:07
9*.2*.6*.5*:7777 17*.6*.13*.15*:39286
2012-02-01 09:17:07 2012-02-01 09:17:07
9*.2*.6*.5*:7777 17*.6*.13*.15*:48431
2012-02-01 09:17:07 2012-02-01 09:17:07
... and so on
second time it attacks a few ips in the same range:
06:07:33.829922 IP 9*.2*.6*.5*:7777 > **.2*8.67.97.28974:
UDP, length 14
06:07:33.829922 IP 9*.2*.6*.5*:7777 > **.2*8.67.98.28990:
UDP, length 14
06:07:33.837922 IP 9*.2*.6*.5*:7777 > **.2*8.67.96.28971:
UDP, length 14
06:07:33.841921 IP 9*.2*.6*.5*:7777 > **.2*8.67.98.28990:
UDP, length 14
06:07:33.841921 IP 9*.2*.6*.5*:7777 > **.2*8.67.97.28974:
UDP, length 14
... and so on
(ips partially censored)
The port of the source (7777) is our samp server...
Server version is Linux.
Outgoing traffic exceeded 300mbit.
The outgoing connection attempts (e.g the udp floods) do not show in the samp log file.
It, obviously, lags the sh*t out of the players, causing timeouts.
is this a known issue and fixable?
i suppose this could be a serious security gab in the server software... once this "tool" or "technique" is out there it can be very damaging for many samp servers and/or communities...