1 (edited by Deepfinder 2018-08-19 16:10:17)

Topic: RIP Teeworlds

No one likes to say it, but it must now be said now. Teeworlds has been killed by the new hack (the "(connecting)" bots). That there is still no official statement clarifies this.
Players turn, will soon turn away. I don't want to say too many words about it, it's just over now.
Better a quick death than a slow one.


† Teeworlds: 2007 - 2018

I will be banned if I troll again ...

2

Re: RIP Teeworlds

Teeworlds isn't dead yet. Not all servers are affected and the attacker does not seem to update their server list very often. There are still plenty of players online. Use the filter "server not full", sort by players online and skip down the list until you find a server that isn't almost full of "(connecting)".

3

Re: RIP Teeworlds

encypruon wrote:

Teeworlds isn't dead yet

Yet. I give it 2 - 3 months.

I will be banned if I troll again ...

4

Re: RIP Teeworlds

What a constructive message. Anyone who really still wants the play the game can always play it. Yes this attack sucks. There is a patch available here https://github.com/axblk/teeworlds/tree/0.6-improved
With this commit patching the vulnerability https://github.com/axblk/teeworlds/comm … b8d92cd1ac
(I think it was merged from ddnet)
There's no official release fixing this yet but anyone could go fix their server and reboot them and it would be fine.
Sometimes I feel people find it fun to say the game is dead instead of trying to fix it or just playing it / inviting more people to play.

5 (edited by Stitch626 2018-08-21 19:00:52)

Re: RIP Teeworlds

It's not allowed to host a modified vanilla server (as DM,CTF, etc), no matter what kind of edit it is.

6 (edited by Schwertspize 2018-08-21 21:35:11)

Re: RIP Teeworlds

Deepfinder wrote:

No one likes to say it, but it must now be said now. Teeworlds has been killed by the new hack (the "(connecting)" bots). That there is still no official statement clarifies this.
Players turn, will soon turn away. I don't want to say too many words about it, it's just over now.
Better a quick death than a slow one.


† Teeworlds: 2007 - 2018


This is exactly what an attacker wants to achieve. Besides, the community is now no worse than it was the past months.

Besides, such "security fixes" which are basically just careful filtering of packets, no matter whether it's dumb or some kind of intelligent, could as well be implemented in a firewall running as a seperate entity and looking into the packets. Also, each master ban is always at the moderator's discretion.

Having troubles finding servers in the serverlist? Go to Pastebin (its a referer cause there is daily a new pastebin) and add the lines to your settings.cfg (in %APPDATA%\teeworlds). Then open teeworlds and go to the favorites tab. (Note however, standard teeworlds client can only show 256 favorites, use ddnet instead)

7

Re: RIP Teeworlds

Fudgyking wrote:

There is a patch available here https://github.com/axblk/teeworlds/tree/0.6-improved
With this commit patching the vulnerability https://github.com/axblk/teeworlds/comm … b8d92cd1ac
(I think it was merged from ddnet)

The commit you've linked to only limits how many player lists are send out per second (to clients looking for servers), but AFAIK that not the main problem right now.

The attacker appears to be using that it is possible to occupy slots without ever receiving and responding to a reply from the server. Right now taking up a slot is as easy as sending one UDP packet with the right content to the server. This leads to the many "(connecting)" clients that clog the servers. I tested it offline, trying to replicate the attack.

Stopping the attack might be possible by blacklisting the IPs that try to connect too often over and over a long period of time, but if the attackers ISP lets them forge their source IP address, they can make up as many addresses as they want (but only for sending, not receiving). In that case it is necessary add some kind of token to the protocol. Unfortunately that needs changes in both the server and the client. Maybe it is possible to improvise by putting a token (generated specifically for each player) in the server name and having them use it as a password. Unfortunately right now players already take up a slot when they are looking at the password prompt and the slot number appears to double as the player id (Not quite sure, don't quote me on that) making this a difficult to implement.

I did not have a server running before the attack started and the attacker does not appear to refresh their sever list so this is mostly guesswork.

Another idea to at least make the attack more difficult is to modify the server to not refuse new clients when the server is full of "clients" that aren't fully connected and instead randomly drop one of the other clients. This way the attacker can not block the server completely, just reduce the probability of a successful connection. Of course that's a rather dirty solution but at least it's very easy to implement. Here (https://pastebin.com/4Bj8mPnt) is a patch doing exactly that, but I wouldn't advice anyone to use it because it is barely tested, still has some printline debugging in it and is easy to circumvent for the attacker. At least it works against my test attack script.

8

Re: RIP Teeworlds

In the end, yes, it's an intrinsic problem within the teeworlds protocol, a design mistake. Just as a side note, I first thought the servers were filled solely to enlarge the server status response which could easily be abused for an amplification attacks (and I even noticed at least one attack being performed that way). It's just yet another vulnerability that's there.

Having troubles finding servers in the serverlist? Go to Pastebin (its a referer cause there is daily a new pastebin) and add the lines to your settings.cfg (in %APPDATA%\teeworlds). Then open teeworlds and go to the favorites tab. (Note however, standard teeworlds client can only show 256 favorites, use ddnet instead)

9

Re: RIP Teeworlds

† Teeworlds: 2007 - 2018

Hope it gets solved soon.
https://78.media.tumblr.com/7a6782d1bc26857661a40a9d5057c9f7/tumblr_inline_oncg7euMNa1s6v1eo_1280.png

Playing Teeworlds since 2011!
"I will always be topless for you"
                  - Günther Branlutte

10 (edited by jxsl13 2018-08-23 16:42:31)

Re: RIP Teeworlds

This is the actual ddnet patch, that exists since about 2015:

this is the original since 2015: https://github.com/east/teeworlds/commi … _antispoof
updated here:https://github.com/eeeee/ddnet/commit/4 … e61c7d56e6

patched ddnet vanilla servers here: https://github.com/Learath2/teeworlds/c … catchspoof

Learath2 also seems to have patched other vanilla mods, which you could search for.

Teeworlds[ friends ] clan
Some YouTube Stuff about Teeworlds

11

Re: RIP Teeworlds

Can anyone confirm if / which of these patches solves the attack problem and still allows me to run vanilla servers, or if there's going to be an official patch? I'd love to keep running my teeworlds servers but the machine is also used for many other things and I can't afford to have its bandwidth flooded by these attacks. I've had to shut my servers down. I know this is what the attacker wants, but like I said I can't afford to lose access to the machine.

12

Re: RIP Teeworlds

antisol wrote:

Can anyone confirm if / which of these patches solves the attack problem and still allows me to run vanilla servers, or if there's going to be an official patch? I'd love to keep running my teeworlds servers but the machine is also used for many other things and I can't afford to have its bandwidth flooded by these attacks. I've had to shut my servers down. I know this is what the attacker wants, but like I said I can't afford to lose access to the machine.

This is the correct link: https://github.com/eeeee/ddnet/commit/4 … 61c7d56e6.

I'm sorry that there hasn't been an official patch so far.