TShock allows chat while not fully connected, possible ban evasion
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-285.
Summary
This issue was reported to TShock by @ohayo, but was found by the Discord user by the name of `sofurry.com`. Please note that this user **does not own this domain on the internet, just the discord handle**. TShock overrides certain Terraria vanilla systems, including chat, and the connection handling, for its own purposes, like enforcing bans. When clients connect but do not complete the connection handshake (e.g., send message number 6), they can "exist" on the server, occupy a player slot, chat, and receive data from the server despite not being fully connected. Individuals who exploit this will be able to effectively harass the server, observe the server, and utilize server resources even if banned from the server. For servers that operate with a proxy that strictly enforces the connection handshake/sequence, this is not an issue, but for smaller servers or servers running vanilla TShock this is an issue worth patching for. PR body supplied by @ohayo (patch writer): Terraria's standard server by default checks for bans upon the client sending the ConnectRequest packet, however, TShock instead chooses to check if the client connecting is banned upon the Request World Data packet. A malicious client can easily just not send this packet, and still join the server even while being banned. Also by not sending Request World Data, the malicious client is still able to receive all packets from the server & even chat. Other clients will not be notified of their join/leave but will be able to see them on the player list. Leading to potential chat spam & "spying" on packets of players within the server.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | TShock (NuGet) | before 5.2.2 | 5.2.2 | Patch available | GHSA-f8mx-cwfh-7hr2 |
- TShock (NuGet) Vendor— Affected before 5.2.2 Fixed in 5.2.2 Patch available GHSA-f8mx-cwfh-7hr2
Remediation
- Fix · GHSA-f8mx-cwfh-7hr2 TShock (NuGet) Fixed in 5.2.2 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-f8mx-cwfh-7hr2
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences