tgstation-server is a production scale tool for BYOND server management. Prior to 6.8.0, low permission users using the "Set .dme Path" privilege could potentially set malicious .dme files existing on the host machine to be compiled and executed. These .dme files could be uploaded via tgstation-server (requiring a separate, isolated privilege) or some other means. A server configured to execute in BYOND's trusted security level (requiring a third separate, isolated privilege OR being set by another user) could lead to this escalating into remote code execution via BYOND's shell() proc. The ability to execute this kind of attack is a known side effect of having privileged TGS users, but normally requires multiple privileges with known weaknesses. This vector is not intentional as it does not require control over the where deployment code is sourced from and _may_ not require remote write access to an instance's `Configuration` directory. This problem is fixed in versions 6.8.0 and above.
Summary
AIBefore 6.8.0, a low-permission user with the “Set .dme Path” privilege could select a malicious .dme file already on the host for compilation and execution. If the server runs at BYOND’s trusted security level, this could escalate to remote code execution via BYOND’s shell() proc; that configuration requires a separate privilege or action by another user.
Who should check
Operators using NuGet Tgstation.Server.Api or Tgstation.Server.Host versions 4.0.0 through versions before 6.8.0 should check their installations.
What to do
- 1Update Tgstation.Server.Api and Tgstation.Server.Host to 6.8.0 or later.