Loading...
Skip to main content

GHSA-f8mx-cwfh-7hr2 — Vulnerability in TShock — Advisory Details

MEDIUM

TShock allows chat while not fully connected, possible ban evasion

Published February 3, 2025Updated February 3, 2025Source: osv

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.

Advisory Timeline

  • First published February 3, 2025 (616 days ago).
  • Last revised February 3, 2025 — 0 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

NuGet
Update TShock to 5.2.2 or later
dotnet add package TShock --version 5.2.2

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (1)

Affects 1 ecosystem: nuget (1).

PackageEcosystemAffectedFixed In
TShock
nuget
5.0.0, 5.0.0-beta, 5.1.0, 5.1.1 (+4 more)5.2.2

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-285
    Improper AuthorizationMITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 7.3 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
—
Confidentiality
—
Integrity
—
Availability
—

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Frequently Asked Questions

What is GHSA-f8mx-cwfh-7hr2?
TShock allows chat while not fully connected, possible ban evasion This vulnerability has been assigned a severity rating of MEDIUM (CVSS score: 7.3/10).
How do I check if my project is affected by GHSA-f8mx-cwfh-7hr2?
GHSA-f8mx-cwfh-7hr2 affects TShock. Use GeekWala's free vulnerability scanner to check your dependencies against GHSA-f8mx-cwfh-7hr2 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
7.3

High exploitability or significant impact. Prioritize remediation within days.

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies