CVE-2023-2917
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 · uneditedThe Rockwell Automation Thinmanager Thinserver is impacted by an improper input validation vulnerability. Due to an improper input validation, a path traversal vulnerability exists, via the filename field, when the ThinManager processes a certain function. If exploited, an unauthenticated remote attacker can upload arbitrary files to any directory on the disk drive where ThinServer.exe is installed. A malicious user could exploit this vulnerability by sending a crafted synchronization protocol message and potentially gain remote code execution abilities.
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 confidenceThe ThinManager Thinserver suffers from an improper input validation vulnerability enabling path traversal via the filename field during synchronization protocol message processing. An unauthenticated remote attacker can upload arbitrary files to any directory on the disk where ThinServer.exe resides, potentially achieving remote code execution.
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>= 11.0.0, <= 11.0.6>= 11.1.0, <= 11.1.6>= 11.2.0, <= 11.2.7>= 12.0.0, <= 12.0.5>= 12.1.0, <= 12.1.6>= 13.0.0, <= 13.0.2= 13.1.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.1/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.
-
Locate ThinServer.exe installationSearch the system for ThinServer.exe and identify its parent directory. Common paths may include C:\Program Files\ThinManager or similar. Note the installation path.Affected if ThinServer.exe is found on the system and the synchronization protocol service is running.
-
Identify ThinManager Thinserver versionRight-click ThinServer.exe, select Properties, and check the File Version field under the Details tab. Alternatively, check the ThinManager application or registry for the installed version number.Affected if The installed version falls within any of these ranges: 11.0.0-11.0.6, 11.1.0-11.1.6, 11.2.0-11.2.7, 12.0.0-12.0.5, 12.1.0-12.1.6, 13.0.0-13.0.2, or 13.1.0 exactly.
-
Verify synchronization protocol exposureCheck network listening ports on the system using 'netstat -an' or similar tools. ThinManager Thinserver uses a synchronization protocol on a configurable port (check ThinManager configuration for the port number). Determine if this port is bound to 0.0.0.0 or an externally accessible IP address.Affected if The synchronization protocol port is listening on a reachable network interface and the system is affected by the vulnerable version range.
-
Inspect ThinServer directory for unauthorized filesExamine the ThinServer.exe directory and parent directories for any unexpected or newly created files, particularly executable files (.exe, .dll, .bat, .ps1) or scripts that were not intentionally deployed.Affected if Unexpected executable or script files are present in the ThinServer directory structure, indicating potential exploitation.
-
Review ThinManager logs for suspicious activityCheck ThinManager log files in the installation directory or logs folder for synchronization protocol messages containing unusual paths (such as ../../../), multiple failed messages, or unexpected file transfer operations.Affected if Logs show path traversal patterns or unexpected file write operations via the synchronization protocol.
The system is affected if ThinManager Thinserver is installed with a version matching any of the vulnerable ranges AND the synchronization protocol port is network-accessible.
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.
From vendor dataApply available vendor patches for ThinManager; if no patch exists, implement network segmentation to restrict access to Thinserver and monitor for suspicious synchronization protocol messages.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2917 — 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-2023-2917 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