I’ve heard back and this described behavior is not in correlation with the mentioned CVE and you are rather facing a replay attack through UDP.
With our current architecture we’re unable to provide any fix for TeamSpeak 3 servers, however we want to prevent this behavior with future TeamSpeak 6 servers. No ETA yet.
Just to clarify, this is not really a vulnerability in the TeamSpeak 3 server itself that can simply be patched. What you are seeing is a replay/amplification pattern that can happen with UDP-based communication in certain network setups.
Because of that, the mitigation is usually not something that can be solved inside the application alone. It needs to be handled at the infrastructure or network level. In practice, this means things like using a hosting provider with proper anti-DDoS and anti-spoofing protection, applying firewall rules or rate limits where possible, and working with your provider so they can trace and filter the traffic upstream.
We also provide a Linux netfilter module that may help in these cases:
For current TS3 deployments, the server should ideally run in an environment where the network layer provides protection against these kinds of traffic patterns.
If you keep receiving abuse reports, your hosting provider should be the right point of contact, as they are usually best positioned to help mitigate this on their side.