{"answers":{"affected":"2 open source packages ship an affected version, including TShock.","exploited":"There is no known exploitation of GHSA-f8mx-cwfh-7hr2 in the wild and no public exploit code.","fix":"Upgrade TShock to 5.2.2 or later.","what":"GHSA-f8mx-cwfh-7hr2 is an authentication bypass vulnerability in TShock, published on 3 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-f8mx-cwfh-7hr2 and fix it if it is affected.\n\nWhat it is: GHSA-f8mx-cwfh-7hr2 is an authentication bypass vulnerability in TShock, published on 3 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-f8mx-cwfh-7hr2 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- TShock (NuGet): affected all versions; fixed in 5.2.2\n- TShock (NuGet): affected all versions; fixed in 5.2.2\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-f8mx-cwfh-7hr2/ (Markdown: https://insights.sbomify.com/GHSA-f8mx-cwfh-7hr2/index.md)","id":"GHSA-f8mx-cwfh-7hr2","markdown":"https://insights.sbomify.com/GHSA-f8mx-cwfh-7hr2/index.md","name":"GHSA-f8mx-cwfh-7hr2","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"TShock server plugin","requires_auth":"none","summary":"Banned users can bypass restrictions and spy on server data by skipping the connection handshake, allowing harassment and unauthorized observation.","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":"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**.\n\nTShock 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.\n\nFor 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.\n\nPR body supplied by @ohayo (patch writer):\n\nTerraria'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.\n\nA malicious client can easily just not send this packet, and still join the server even while being banned.\nAlso by not sending Request World Data, the malicious client is still able to receive all packets from the server \u0026 even chat. \n\nOther clients will not be notified of their join/leave but will be able to see them on the player list.\nLeading to potential chat spam \u0026 \"spying\" on packets of players within the server.","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 allows chat while not fully connected, possible ban evasion","id":"GHSA-f8mx-cwfh-7hr2","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"NuGet","fixed":["5.2.2"],"introduced":["0"],"last_affected":[],"package":"TShock","purl":null,"source":"GHSA-f8mx-cwfh-7hr2"},{"ecosystem":"NuGet","fixed":["5.2.2"],"introduced":["0"],"last_affected":[],"package":"TShock","purl":"pkg:nuget/TShock","source":"GHSA-f8mx-cwfh-7hr2"}],"products":null,"published":"2025-02-03","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":"Banned users can bypass restrictions and spy on server data by skipping the connection handshake, allowing harassment and unauthorized observation.","url":"https://insights.sbomify.com/GHSA-f8mx-cwfh-7hr2/"}