GHSA-c3h4-9gc2-f7h4
HIGHtgstation-server's DreamMaker environment files outside the deployment directory can be compiled and ran by insufficiently permissioned users
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
Tgstation.Server.Api.NETTgstation.Server.HostReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Tgstation.Server.Api | ≥ 4.0.0&&< 6.8.0 | 6.8.0 |
| .NETNuGet | Tgstation.Server.Host | ≥ 4.0.0&&< 6.8.0 | 6.8.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Tgstation.Server.Api. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update Tgstation.Server.Api to 6.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c3h4-9gc2-f7h4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-c3h4-9gc2-f7h4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-c3h4-9gc2-f7h4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-c3h4-9gc2-f7h4 in your dependencies?
O3 detects GHSA-c3h4-9gc2-f7h4 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.