This thread is for discussion and feedback for the 3.2.5 release of the TeamSpeak Client.
Please see the announcement for changelog / features.
We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020
This thread is for discussion and feedback for the 3.2.5 release of the TeamSpeak Client.
Please see the announcement for changelog / features.
When sending PMs please make sure to include a reference link to the thread in question in the body of your message.
I wonder why you even bothered to patch, if you try it you end up with
<20:33:04> Trying to resolve hostname voice.teamspeak.com -platformpluginpath \\192.168.131.152\share
<20:33:04> Failed to resolve hostname 'voice.teamspeak.com -platformpluginpath \\192.168.131.152\share'
anyways
The important question is, how is this exploitable?
By textchat to other users?? That would be a true desaster..
Regards
We have verified and tested a way to exploit this, I was merely saying that we haven't yet found a way to exploit this using the built-in textchat.
After verifying that we are affected it was more important to use to get the fix out, rather than spent that time finding all the possible combinations this can be exploited.
I always try to avoid speaking in absolutes. I strongly believe that it is not possible to exploit this using the textchat,
but there are always things that you overlook in a large code base or things to try that you couldn't think of.
If this is a security update, why not introduce something that prompts the client to update directly. Otherwise, the client can not be used. There are so many users who not see the announcements in the forum or even ignore the update.
There are currently 1 users browsing this thread. (0 members and 1 guests)