Exploit in 0.4.3777.19 ?

[elraro]

Well, i have a problem. Evert 55 min aprox, ALL MY DEDICATED SERVER (Xeon E3) lags like hell. Some exploit in login server? idk...

Log port 7172

tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes

^C61 packets captured
1789294 packets received by filter
1789203 packets dropped by kernel

14:18:53.010440 IP (tos 0x0, ttl 52, id 23898, offset 0, flags [none], proto TCP (6), length 44)
  196.204.13.186.2281 > 178.33.161.190.7172: Flags [S], cksum 0x180b (correct), seq 233432406, win 512, options [mss 1440], length 0
14:18:53.010488 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 44)
  178.33.161.190.7172 > 196.204.13.186.2281: Flags [S.], cksum 0x5117 (correct), seq 1241285990, ack 233432407, win 14600, options [mss 1460], length 0
14:18:53.010492 IP (tos 0x0, ttl 52, id 59874, offset 0, flags [none], proto TCP (6), length 44)
  ABTS-mum-static-204.98.169.122.airtelbroadband.in.2284 > 178.33.161.190.7172: Flags [S], cksum 0x2291 (correct), seq 947572118, win 512, options [mss 1440], length 0
14:18:53.010508 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 44)
  178.33.161.190.7172 > ABTS-mum-static-204.98.169.122.airtelbroadband.in.2284: Flags [S.], cksum 0xc18a (correct), seq 1373892424, ack 947572119, win 14600, options [mss 1460], length 0
14:18:53.010510 IP (tos 0x0, ttl 52, id 54244, offset 0, flags [none], proto TCP (6), length 44)
  lb1.us1.lqm.io.2283 > 178.33.161.190.7172: Flags [S], cksum 0xe77a (correct), seq 1262164489, win 512, options [mss 1440], length 0
14:18:53.010525 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 44)
  178.33.161.190.7172 > lb1.us1.lqm.io.2283: Flags [S.], cksum 0x0ebb (correct), seq 4171244138, ack 1262164490, win 14600, options [mss 1460], length 0
14:18:53.010528 IP (tos 0x0, ttl 52, id 40245, offset 0, flags [none], proto TCP (6), length 44)
  106.0.255.94.2287 > 178.33.161.190.7172: Flags [S], cksum 0x2459 (correct), seq 645157188, win 512, options [mss 1440], length 0
14:18:53.010546 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 44)
  178.33.161.190.7172 > 106.0.255.94.2287: Flags [S.], cksum 0xeb34 (correct), seq 3151060508, ack 645157189, win 14600, options [mss 1460], length 0
14:18:53.010549 IP (tos 0x0, ttl 52, id 38422, offset 0, flags [none], proto TCP (6), length 44)
  253.47.89.164.2293 > 178.33.161.190.7172: Flags [S], cksum 0x3aa9 (correct), seq 1614222048, win 512, options [mss 1440], length 0
14:18:53.010564 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 44)
  178.33.161.190.7172 > 253.47.89.164.2293: Flags [S.], cksum 0xd79e (correct), seq 2158085128, ack 1614222049, win 14600, options [mss 1460], length 0
14:18:53.010566 IP (tos 0x0, ttl 52, id 24571, offset 0, flags [none], proto TCP (6), length 44)
  31.121.40.250.2294 > 178.33.161.190.7172: Flags [S], cksum 0xabdc (correct), seq 594470596, win 512, options [mss 1440], length 0
14:18:53.010580 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 44)
  178.33.161.190.7172 > 31.121.40.250.2294: Flags [S.], cksum 0x0424 (correct), seq 3811683383, ack 594470597, win 14600, options [mss 1460], length 0
14:18:53.010582 IP (tos 0x0, ttl 52, id 44491, offset 0, flags [none], proto TCP (6), length 44)
  dialup-62-11-208-223.clienti.tiscali.it.2298 > 178.33.161.190.7172: Flags [S], cksum 0xfd92 (correct), seq 322921667, win 512, options [mss 1440], length 0
14:18:53.010597 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 44)
  178.33.161.190.7172 > dialup-62-11-208-223.clienti.tiscali.it.2298: Flags [S.], cksum 0xaa0c (correct), seq 3684817299, ack 322921668, win 14600, options [mss 1460], length 0
14:18:53.010599 IP (tos 0x0, ttl 52, id 50639, offset 0, flags [none], proto TCP (6), length 44)
  tamc084197p.tamc.amedd.army.mil.2302 > 178.33.161.190.7172: Flags [S], cksum 0xbffb (correct), seq 73011138, win 512, options [mss 1440], length 0
14:18:53.010614 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 44)
  178.33.161.190.7172 > tamc084197p.tamc.amedd.army.mil.2302: Flags [S.], cksum 0xf6d7 (correct), seq 510696241, ack 73011139, win 14600, options [mss 1460], length 0
14:18:53.010616 IP (tos 0x0, ttl 52, id 45985, offset 0, flags [none], proto TCP (6), length 44)
  22.29.176.41.2304 > 178.33.161.190.7172: Flags [S], cksum 0x0894 (correct), seq 1078651195, win 512, options [mss 1440], length 0
14:18:53.010631 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 44)
  178.33.161.190.7172 > 22.29.176.41.2304: Flags [S.], cksum 0xe7cd (correct), seq 857463667, ack 1078651196, win 14600, options [mss 1460], length 0
14:18:53.010633 IP (tos 0x0, ttl 52, id 12514, offset 0, flags [none], proto TCP (6), length 44)
  59.191.84.223.2312 > 178.33.161.190.7172: Flags [S], cksum 0x19fc (correct), seq 1108380509, win 512, options [mss 1440], length 0
14:18:53.010633 IP (tos 0x0, ttl 52, id 12514, offset 0, flags [none], proto TCP (6), length 44)
  59.191.84.223.2312 > 178.33.161.190.7172: Flags [S], cksum 0x19fc (correct), seq 1108380509, win 512, options [mss 1440], length 0
14:18:53.010648 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 44)
  178.33.161.190.7172 > 59.191.84.223.2312: Flags [S.], cksum 0xaf16 (correct), seq 2334281180, ack 1108380510, win 14600, options [mss 1460], length 0
14:18:53.010650 IP (tos 0x0, ttl 52, id 47981, offset 0, flags [none], proto TCP (6), length 44)
  11.223.143.242.2310 > 178.33.161.190.7172: Flags [S], cksum 0x3bd7 (correct), seq 1083216247, win 512, options [mss 1440], length 0
14:18:53.010665 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 44)
  178.33.161.190.7172 > 11.223.143.242.2310: Flags [S.], cksum 0x3fd5 (correct), seq 3395644943, ack 1083216248, win 14600, options [mss 1460], length 0
14:18:53.010667 IP (tos 0x0, ttl 52, id 7648, offset 0, flags [none], proto TCP (6), length 44)
  c-174-61-1-30.hsd1.fl.comcast.net.2315 > 178.33.161.190.7172: Flags [S], cksum 0x11ec (correct), seq 1209981626, win 512, options [mss 1440], length 0
14:18:53.010683 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 44)
  178.33.161.190.7172 > c-174-61-1-30.hsd1.fl.comcast.net.2315: Flags [S.], cksum 0x3d10 (correct), seq 1247448191, ack 1209981627, win 14600, options [mss 1460], length 0
14:18:53.010685 IP (tos 0x0, ttl 52, id 35160, offset 0, flags [none], proto TCP (6), length 44)
  110.41.222.175.2309 > 178.33.161.190.7172: Flags [S], cksum 0x7117 (correct), seq 718350211, win 512, options [mss 1440], length 0

 

[dominique120]

Yes that rev has a know bug that can be exploited by players. I recommend you get a premium account and get the 5196 rev that is downgraded to 8.60

 

[WibbenZ]

Yes that rev has a know bug that can be exploited by players. I recommend you get a premium account and get the 5196 rev that is downgraded to 8.60

Do note that you will have to do ALOT of modifications to make it work(was atleast with the one I found when I was a premmy user).
Id use a normal 3777 or a normal 3884 without any changes.

 

[elraro]

is a SYN attack... what can i do?

 

[dominique120]

To quote the guy who found the bug:

[ DO NOT USE THIS REV ]
Instead of it use this rev. Or you can still use this rev if you can fix that crashbug

I was using this rev on Vestia.pl and someone found out how to crash it.
It crashes when someone send some kind of attack on server (propably SYN FLOOD)

And here's one of many crashlogs:

#0  0x00007f16165621b5 in raise () from /lib/libc.so.6
#1  0x00007f1616564fc0 in abort () from /lib/libc.so.6
#2  0x00007f1616df6dc5 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
#3  0x00007f1616df5166 in ?? () from /usr/lib/libstdc++.so.6
#4  0x00007f1616df5193 in std::terminate() () from /usr/lib/libstdc++.so.6
#5  0x00007f1616df528e in __cxa_throw () from /usr/lib/libstdc++.so.6
#6  0x000000000043b3e7 in void boost::throw_exception<boost::system::system_error>(boost::system::system_error const&) ()
#7  0x000000000043b9a7 in boost::asio::detail::posix_mutex::lock() ()
#8  0x000000000043b9d1 in boost::asio::detail::scoped_lock<boost::asio::detail::posix_mutex>::scoped_lock(boost::asio::detail::posix_mutex&) ()
#9  0x000000000043c161 in boost::asio::detail::deadline_timer_service<boost::asio::time_traits<boost::posix_time::ptime>, boost::asio::detail::epoll_reactor<false> >::cancel(boost::asio::detail::deadline_timer_service<boost::asio::time_traits<boost::posix_time::ptime>, boost::asio::detail::epoll_reactor<false> >::implementation_type&, boost::system::error_code&) ()
#10 0x000000000043c2ab in boost::asio::basic_deadline_timer<boost::posix_time::ptime, boost::asio::time_traits<boost::posix_time::ptime>, boost::asio::deadline_timer_service<boost::posix_time::ptime, boost::asio::time_traits<boost::posix_time::ptime> > >::~basic_deadline_timer() ()
#11 0x000000000043e7bf in Connection::~Connection() ()
#12 0x0000000000425f37 in boost::detail::shared_count::~shared_count() ()
#13 0x000000000043add6 in std::_List_base<boost::shared_ptr<Connection>, std::allocator<boost::shared_ptr<Connection> > >::_M_clear() ()
#14 0x000000000043e71c in ConnectionManager::~ConnectionManager() ()
#15 0x00007f1616566612 in ?? () from /lib/libc.so.6
#16 0x00007f1616566665 in exit () from /lib/libc.so.6
#17 0x00007f161654ec94 in __libc_start_main () from /lib/libc.so.6
#18 0x00000000004168c9 in _start ()

Use the newer rev, sure you might have to do some changes in the libs and scripts but its alot more stable and does not have this problem

 

[WibbenZ]

To quote the guy who found the bug:

Use the newer rev, sure you might have to do some changes in the libs and scripts but its alot more stable and does not have this problem

I hope you are joking, just changing the libs, scripts etc is a plain reinstallation you always to that. The thing with the 5xxx revs is that you have to change all doors in the map(atleast was when I tried it) and some other major things I think.
But as you want there are ALOT of users that use 3777 and 3884, never heard of something like this.

 

[Crypton3]

To quote the guy who found the bug:

Use the newer rev, sure you might have to do some changes in the libs and scripts but its alot more stable and does not have this problem

I have mistaken You can use this rev, but remember to set proper ulimit in Linux, otherwise it would be possible to crash your TFS.