Impact
What kind of vulnerability is it? Who is impacted?
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.
Patches
Has the problem been patched? What versions should users upgrade to?
This problem is patched by pull request #1835 and fixed in versions 6.8.0 and above.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Do not give un-trusted users the Deployment permission to set a .dme path on instances.
Impact
What kind of vulnerability is it? Who is impacted?
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
Configurationdirectory.Patches
Has the problem been patched? What versions should users upgrade to?
This problem is patched by pull request #1835 and fixed in versions 6.8.0 and above.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Do not give un-trusted users the Deployment permission to set a .dme path on instances.