- Apr 25, 2015
- 1,845
- 2
- 2,199
- 327
PLEASE NOTICE: TeamSpeak staff have been working hard to make the security of TeamSpeak 3 stronger. I am happy to say that everything below is already fixed. We are still finding more bugs and security issues in this VOIP platform although the TeamSpeak developers have been cooperative with us by accepting our reports. I no longer believe that "TeamSpeak Sucks", the security was not the best although it is getting better and I feel that TeamSpeak security is getting strengthened/hardened with each vulnerability/bug the R4P3 Security Team forwards on to the developers.
TeamSpeak 3 has many security vulnerabilities that have been found by researchers from R4P3, we are security enthusiasts that enjoy trying to stay safe online. Some of the security issues are:
TeamSpeak 3 has many security vulnerabilities that have been found by researchers from R4P3, we are security enthusiasts that enjoy trying to stay safe online. Some of the security issues are:
- Buffer Overflow (?) from a BB Code handling issue with the QT Framework. Mumble also suffered from the same vulnerability although Mumble patched within a few days, TeamSpeak 3 was not patched for over 2 months.
- Deadlock (hang/error/crash) in the server process, any user could remotely crash a TeamSpeak 3 server. This would disable everyone in the server from talking for 10-30 seconds (disconnected) until every users client times out and everyone drops off the server. The server then must be manually restarted (default) by the server owner unless there is an auto-restart script.
- BB Code was accepted in nicknames and you could easily spam an entire server with links.
Last edited: