{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-34243 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-34243 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-34243 is a medium-severity vulnerability in tgstation-server, published on 8 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-34243 and fix it if it is affected.\n\nWhat it is: CVE-2023-34243 is a medium-severity vulnerability in tgstation-server, published on 8 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-34243 in the wild and no public exploit code.\n\nAffected product: tgstation-server. No package-level version data is available, so check the vendor advisory linked from the reference page.\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/CVE-2023-34243/ (Markdown: https://insights.sbomify.com/CVE-2023-34243/index.md)","id":"CVE-2023-34243","markdown":"https://insights.sbomify.com/CVE-2023-34243/index.md","name":"CVE-2023-34243","record":{"aliases":["GHSA-w3jx-4x93-76ph"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"BYOND server management","requires_auth":"none","summary":"Attackers can discover Windows usernames by brute-forcing the login endpoint due to distinct responses for valid logons.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"tgstation-server","vendor":"tgstation13"}],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"TGstation is a toolset to manage production BYOND servers. In affected versions if a Windows user was registered in tgstation-server (TGS), an attacker could discover their username by brute-forcing the login endpoint with an invalid password. When a valid Windows logon was found, a distinct response would be generated. This issue has been addressed in version 5.12.5. Users are advised to upgrade. Users unable to upgrade may be mitigated by rate-limiting API calls with software that sits in front of TGS in the HTTP pipeline such as fail2ban.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Windows user name disclosure in TGstation","id":"CVE-2023-34243","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"GLPI vulnerable to reflected XSS in search pages","id":"CVE-2023-34244"},"packages":[],"prev":{"headline":"Cilium vulnerable to information leakage via incorrect ReferenceGrant handling","id":"CVE-2023-34242"},"products":["tgstation-server"],"published":"2023-06-08","related":[{"cvss_score":9.8,"headline":"tgstation-server cached user logins in legacy server","id":"CVE-2018-17107","kev_date_added":null,"published":"2018-09-24"},{"cvss_score":8.8,"headline":"tgstation-server's role authorization incorrectly OR'd with user's enabled status","id":"CVE-2025-21611","kev_date_added":null,"published":"2025-01-06"},{"cvss_score":8.4,"headline":"tgstation-server's DreamMaker environment files outside the deployment directory can be compiled and ran by insufficiently permissioned users","id":"CVE-2024-41799","kev_date_added":null,"published":"2024-07-29"},{"cvss_score":7.7,"headline":"Insufficiently Protected ChatBot Credentials in tgstation-server","id":"CVE-2023-32687","kev_date_added":null,"published":"2023-05-29"},{"cvss_score":7.7,"headline":"Path traversal in n/a","id":"CVE-2020-16136","kev_date_added":null,"published":"2020-07-31"},{"cvss_score":6.1,"headline":"Incorrectly Specified Chat Message Destinations in tgstation-server and DreamMaker API","id":"CVE-2023-33198","kev_date_added":null,"published":"2023-05-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-06","vendors":["tgstation"]},"summary":"Attackers can discover Windows usernames by brute-forcing the login endpoint due to distinct responses for valid logons.","url":"https://insights.sbomify.com/CVE-2023-34243/"}