CVE-2024-41799
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedtgstation-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn tgstation-server before version 6.8.0, users with the 'Set .dme Path' privilege could specify malicious .dme files on the host system to be compiled. When combined with the ability to upload .dme files (requiring a separate privilege) and a server running in BYOND's trusted security level (requiring a third privilege), this allows privilege escalation to remote code execution via BYOND's shell() proc.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 4.0.0, < 6.8.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check tgstation-server versionRun 'tgstation-server --version' or check the server's about/version information page to determine the installed version.Affected if Version is 4.0.0 or higher but lower than 6.8.0
-
Identify users with Set .dme Path privilegeAccess the tgstation-server administration panel or user management configuration and review which roles or users have the 'Set .dme Path' privilege assigned.Affected if Any user account has the 'Set .dme Path' privilege enabled
-
Verify .dme file upload permissionsReview the user permissions or role configuration to determine which users can upload .dme files to the server.Affected if Any user account has permission to upload .dme files to the server
-
Check BYOND security level configurationInspect the server configuration files or administration settings to determine if the server is running in BYOND's trusted security level.Affected if The server is configured to run with BYOND's trusted security level enabled
-
Assess combined privilege exposureCross-reference the above findings to identify if a single user or combination of users has all three required capabilities: Set .dme Path, .dme file upload, and trusted security level is active.Affected if Version is vulnerable AND any user has Set .dme Path privilege AND .dme file upload exists AND server uses trusted security level
You are affected if running tgstation-server version 4.0.0 to 6.7.x and any user has the Set .dme Path privilege while the server operates in BYOND's trusted security level with .dme upload capabilities available.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.8.0
Upgrade to tgstation-server version 6.8.0 or later. Audit and restrict user privilege assignments, ensuring the 'Set .dme Path' privilege is not granted to low-trust users and that the trusted security level is carefully controlled.
6.8.0 or later
- 1. Back up your current tgstation-server configuration and data directory.
- 2. Stop the tgstation-server service.
- 3. Upgrade tgstation-server to version 6.8.0 or later.
- 4. Verify the upgrade was successful by checking the server version.
- 5. Restart the tgstation-server service.
- 6. Review user privileges to ensure only trusted users have the 'Set .dme Path' privilege.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-41799 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-41799 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data