Counter StrikeApplication · Valvesoftware

CVE-2023-38312

HIGH · 7.5 CVSS v3.1 Published 2023-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A directory traversal vulnerability in Valve Counter-Strike 8684 allows a client (with remote control access to a game server) to read arbitrary files from the underlying server via the motdfile console variable.

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 confidence

A directory traversal vulnerability in Valve Counter-Strike allows a client with remote control (RCON) access to read arbitrary files from the server filesystem by manipulating the motdfile console variable with path traversal sequences (e.g., ../../../../etc/passwd). The motdfile variable, used for displaying message-of-the-day files, lacks proper path sanitization.

MitigationUpdate the Counter-Strike game server to the latest patched version. Additionally, restrict RCON/remote control access to trusted IP addresses only via server configuration to reduce the attack surface.

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
Counter StrikeApplication
Affected:= 8684

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Counter-Strike server version
    Execute the 'version' console command on the server or check the server executable version property. On Linux, you can also run './hlds_run -version' or check the 'version.txt' file in the server directory.
    Affected if The installed version is exactly 8684 (this specific build is vulnerable)
  2. Verify RCON is enabled and accessible
    Check the server configuration file (server.cfg or autoexec.cfg) for the 'rcon_password' setting. Also check if the server has any IP-based access restrictions on RCON connections via firewall rules or server startup parameters (-ip flag).
    Affected if RCON password is set and the server accepts remote RCON connections from untrusted networks (not restricted to localhost or specific IPs)
  3. Inspect current motdfile console variable
    Execute 'motdfile' console command via RCON or in the server console to view the current value. Also check config files for any custom motdfile paths.
    Affected if The motdfile variable points to a file location that could be accessed via path traversal (the default is typically a relative path in the server directory)
  4. Test path traversal vulnerability
    From an RCON session, run: 'motdfile ../../../../etc/passwd' then 'motd' to trigger the server to read the file. If the file content appears in the MOTD, the vulnerability is present.
    Affected if The server returns file contents from outside the intended server directory when using path traversal sequences in motdfile

A server is affected if it runs version 8684 with RCON exposed to untrusted networks, and the motdfile variable accepts path traversal sequences to read arbitrary files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Counter-Strike game server to the latest patched version. Additionally, restrict RCON/remote control access to trusted IP addresses only via server configuration to reduce the attack surface.

Fix this in Counter Strike Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-38312 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-38312 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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