CVE-2023-33198
Tgstation13 Tgstation-Server 4.0.0 – 5.12.2
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-33198 is a medium-severity Incorrectly Specified Destination in a Communication Channel (CWE-941) vulnerability in Tgstation13 Tgstation-Server. Its CVSS base score is 6.1 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique NTDS (T1003.003); ranked at the 49th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-37371
Vulnerability Data
tgstation-server is a production scale tool for BYOND server management. The DreamMaker API (DMAPI) chat channel cache can possibly be poisoned by a tgstation-server (TGS) restart and reattach. This can result in sending chat messages to one of any of…
more
the configured IRC or Discord channels for the instance on enabled chat bots. This lasts until the instance's chat channels are updated in TGS or DreamDaemon is restarted. TGS chat commands are unaffected, custom or otherwise.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Network monitoring can detect traffic to wrong destinations but does not prevent the specification error itself.
Documented network data-flow diagrams directly reduce the chance of specifying an incorrect destination address.
Hardened configuration baselines and change control prevent mis-specified endpoints from being deployed.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Network security controls enforce correct endpoint validation and routing, directly preventing mis-specified destinations.
Security of network services includes service endpoint verification, mitigating incorrect destination specification.
Secure SDLC practices can catch destination errors during design, but coverage is indirect.
A.8.26 only requires that security requirements (including those that could address destination validation) be identified and specified during development; it does not itself enforce, implement or prevent the incorrect destination flaw from remaining exploitable.
Secure architecture principles encourage proper endpoint design, providing indirect mitigation.