- Mar 28, 2016
- 530
- 584
- 197
- Thread starter
- #21
Sorry... just me being dumb :x Link in first post updated
R4P3 Client Crash/Anti-Crash [3.0.19.0]
Agusanz
Active Member
- Jul 18, 2015
- 239
- 148
- 88
gamerscor2
Member
- Oct 8, 2015
- 1
- 0
- 33
Looks great good job
DeStRoYzR
Member
- Sep 14, 2015
- 16
- 2
- 38
This link does not work: !!This plugin provides a hotfix addressing a recently discovered vulnerability affecting TeamSpeak3 Client version 3.0.19.0
It also provides a PoC Utility to exploit the vulnerability!
Only use it on your own Server for test purposes!
R4P3.NET wont take responsibility for damage caused.
This doesnt prevent crash if the String is still in the Chatlogs!
Credits go to the exploit's original authors!... and also
Derp: Plugin Development
Kaptan647: Plugin Development
-R4P3-DevTeam // Dedmen
Ramadi
Member
- Mar 12, 2016
- 79
- 19
- 43
- Apr 30, 2015
- 933
- 1,014
- 217
Yeah I'm sure it's the same plugin too!
when i open it , it opens teamspeak3 and don't open install !??
Supervisor
Administrator
- Apr 27, 2015
- 1,863
- 2,550
- 335
Should work again now.
Last edited by a moderator:
- Jan 30, 2016
- 1,334
- 1,146
- 254
Hi there, it's not an application, it's a plugin, therefore you'll need to start it with "package_inst.exe" in the TS3 root directory.1-
2-
Thanks <3
Helpful :*
CreeperTheKing
Member
- Apr 23, 2016
- 5
- 0
- 35
how to use it btw?
I've found some interesting artifacts whilst testing this on my server.
We've had one person become resistant to the malformed message, being able to send it himself (Both using the 3.0.19 client version without the plugin) - the drawback of this immunity, however - Whenever he attempts to connect to the server after a client restart, he immediately times out, crashing to desktop as though the plugin had been used on him.
This has happened to another user, also, who received the message but didn't crash, and is now unable to connect to all servers where it has been used.
In an attempt to rectify the issue, they installed the plugin themselves and deleted their client chat logs, to no avail; they are still unable to connect to the servers.
It's a rather interesting quirk.
We've had one person become resistant to the malformed message, being able to send it himself (Both using the 3.0.19 client version without the plugin) - the drawback of this immunity, however - Whenever he attempts to connect to the server after a client restart, he immediately times out, crashing to desktop as though the plugin had been used on him.
This has happened to another user, also, who received the message but didn't crash, and is now unable to connect to all servers where it has been used.
In an attempt to rectify the issue, they installed the plugin themselves and deleted their client chat logs, to no avail; they are still unable to connect to the servers.
It's a rather interesting quirk.
- Jan 30, 2016
- 1,334
- 1,146
- 254
I had the same issue, couldn't connect to my own server anymore, was unable to remove chat-logs as they kept returning.
Downgraded to 3.0.18.2.
EDIT:
2) ?????
3) Profit
Downgraded to 3.0.18.2.
EDIT:
1) Install plugin
2) ?????
3) Profit
Supervisor
Administrator
- Apr 27, 2015
- 1,863
- 2,550
- 335
If you were crashed before getting the plugin, simply delete/rename your chats in /config/chats/*server*/..
Yes, they zipped them and deleted the logs and that sorted them out, now able to connect to all servers normally.
