Description: Luigi Auriemma has reported some vulnerabilities in Toribash, which can be exploited by malicious people to cause a DoS (Denial of Service) or potentially compromise a vulnerable system.
1) A format string error when processing the nicknames exists within the dedicated server. This can be exploited to crash the server and potentially execute arbitrary code by sending a specially crafted nickname containing format specifiers to a vulnerable server.
2) A buffer overflow when reading overly long game commands (more than 256 bytes) exists within the game client. This can be exploited to cause a buffer overflow and may allow the execution of arbitrary code by e.g. tricking a user into connecting to a malicious server or playing a malicious replay (*.rpl) file.
3) A buffer overflow exists in the game client when handling "SAY" commands without line feeds. This can be exploited to freeze or crash the client and may allow the execution of arbitrary code by e.g. tricking a user into connecting to a malicious server.
4) The server does not initialise data for clients until the "ENTER" command is received. This can be exploited to crash the server by joining a vulnerable server and issuing the "GRID" command before entering the match using the "ENTER" command.
Note: It is also possible to slow down the game server and annoy the game host by sending the bell character (0x07) to a server. It is also reported that attackers can disconnect clients from a server by entering a match and sending an overly long "SPEC" command or emote to the server.
The vulnerabilities are reported in versions 2.71 and prior. Other versions may also be affected.
Solution: Allow only trusted people access to your game server. Do not connect to untrusted servers and do not use replays from untrusted sources.
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
Send Feedback to Secunia
If you have new information regarding this Secunia advisory or a product in our database, please send it to us using either our web form or email us at vuln@secunia.com.
Ideas, suggestions, and other feedback are most welcome.
