CVE-2018-17107
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 · uneditedIn Tgstation tgstation-server 3.2.4.0 through 3.2.1.0 (fixed in 3.2.5.0), active logins would be cached, allowing subsequent logins to succeed with any username or password.
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 · moderate confidenceThe tgstation-server versions 3.2.1.0 through 3.2.4.0 had a flawed login caching mechanism where successful logins were cached, allowing subsequent authentication attempts to succeed with any username or password. This effectively bypasses authentication entirely for any user who has logged in at least once.
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>= 3.2.1.0, < 3.2.5.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Identify tgstation-server versionRun 'tgstation-server --version' or check the service's about/info endpoint, or inspect the binary/file version metadataAffected if The version is 3.2.1.0, 3.2.2.0, 3.2.3.0, or 3.2.4.0
-
Compare version to affected rangeVerify the installed version falls within >= 3.2.1.0 and < 3.2.5.0Affected if The installed version is 3.2.1.0 through 3.2.4.0 inclusive
You are affected if the tgstation-server version is 3.2.1.0 through 3.2.4.0, as these versions contain the flawed login caching mechanism that allows authentication bypass after any successful login.
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 · scoped3.2.5.0
Upgrade to tgstation-server version 3.2.5.0 or later. If immediate upgrade is not possible, consider network-level access controls or temporary disablement of the service until patching can be completed.
3.2.5.0
- Identify the current version of Tgstation Server by checking the server logs or configuration
- Stop the Tgstation Server service to prevent further connections during upgrade
- Download Tgstation Server version 3.2.5.0 or later from the official GitHub repository (github.com/tgstation/tgstation-server)
- Replace the existing installation files with the new version, preserving configuration files
- Start the Tgstation Server service
- Verify the server is running the updated version by checking the startup logs
- Test that authentication is working correctly - attempt login with valid credentials and verify invalid credentials are rejected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17107 — 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-2018-17107 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