{"answers":{"affected":"2 open source packages ship an affected version, including TShock.","exploited":"There is no known exploitation of GHSA-hvm9-wc8j-mgrc in the wild and no public exploit code.","fix":"Upgrade TShock to 5.2.1 or later.","what":"GHSA-hvm9-wc8j-mgrc is an authentication bypass vulnerability in TShock, published on 18 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-hvm9-wc8j-mgrc and fix it if it is affected.\n\nWhat it is: GHSA-hvm9-wc8j-mgrc is an authentication bypass vulnerability in TShock, published on 18 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-hvm9-wc8j-mgrc in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- TShock (NuGet): affected from 4.3.21; fixed in 5.2.1\n- TShock (NuGet): affected from 4.3.21; fixed in 5.2.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-hvm9-wc8j-mgrc/ (Markdown: https://insights.sbomify.com/GHSA-hvm9-wc8j-mgrc/index.md)","id":"GHSA-hvm9-wc8j-mgrc","markdown":"https://insights.sbomify.com/GHSA-hvm9-wc8j-mgrc/index.md","name":"GHSA-hvm9-wc8j-mgrc","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"TShock server plugin","requires_auth":"low_privilege","summary":"Attackers can hijack authenticated sessions by exploiting stale UUIDs in TShock servers with UUID login enabled, allowing unauthorized access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\nAn issue with the way OTAPI manages client connections results in stale UUIDs remaining on `RemoteClient` instances after a player disconnects.\n\nBecause of this, if the following conditions are met a player may assume the login state of a previously connected player:\n1. The server has UUID login enabled\n2. An authenticated player disconnects\n3. A subsequent player connects with a modified client that does not send the `ClientUUID#68` packet during connection\n4. The server assigns the same `RemoteClient` object that belonged to the originally authenticated player to the newly connected player\n\n### Patches\nTShock 5.2.1 hotfixes this issue. A more robust fix will be made to OTAPI itself.\n\n### Workarounds\nImplement a RemoteClient reset event handler in a plugin like so:\n```csharp\npublic override void Initialize()\n{\n        On.Terraria.RemoteClient.Reset += RemoteClient_Reset;\n}\n\nprivate static void RemoteClient_Reset(On.Terraria.RemoteClient.orig_Reset orig, RemoteClient client)\n{\n\tclient.ClientUUID = null;\n        orig(client);\n}\n```","ecosystems":["NuGet"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"TShock Security Escalation Exploit","id":"GHSA-hvm9-wc8j-mgrc","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"NuGet","fixed":["5.2.1"],"introduced":["4.3.21"],"last_affected":[],"package":"TShock","purl":null,"source":"GHSA-hvm9-wc8j-mgrc"},{"ecosystem":"NuGet","fixed":["5.2.1"],"introduced":["4.3.21"],"last_affected":[],"package":"TShock","purl":"pkg:nuget/TShock","source":"GHSA-hvm9-wc8j-mgrc"}],"products":null,"published":"2024-12-18","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can hijack authenticated sessions by exploiting stale UUIDs in TShock servers with UUID login enabled, allowing unauthorized access.","url":"https://insights.sbomify.com/GHSA-hvm9-wc8j-mgrc/"}