TShock
Affected
- introduced
4.3.21, fixed5.2.1(ecosystem)
Fixed versions
5.2.1
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: None
TShock Security Escalation Exploit
Impact
An issue with the way OTAPI manages client connections results in stale UUIDs remaining on RemoteClient instances after a player disconnects.
Because of this, if the following conditions are met a player may assume the login state of a previously connected player:
ClientUUID#68 packet during connectionRemoteClient object that belonged to the originally authenticated player to the newly connected playerPatches
TShock 5.2.1 hotfixes this issue. A more robust fix will be made to OTAPI itself.
Workarounds
Implement a RemoteClient reset event handler in a plugin like so:
public override void Initialize()
{
On.Terraria.RemoteClient.Reset += RemoteClient_Reset;
}
private static void RemoteClient_Reset(On.Terraria.RemoteClient.orig_Reset orig, RemoteClient client)
{
client.ClientUUID = null;
orig(client);
}High Basis: The source's own band: HIGH
4.3.21, fixed 5.2.1 (ecosystem)5.2.1
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0