CVE-2023-27855
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 affected versions, a path traversal exists when processing a message in Rockwell Automation's ThinManager ThinServer. An unauthenticated remote attacker could potentially exploit this vulnerability to upload arbitrary files to any directory on the disk drive where ThinServer.exe is installed. The attacker could overwrite existing executable files with attacker-controlled, malicious contents, potentially causing remote code execution.
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 confidenceA path traversal vulnerability exists in Rockwell Automation's ThinManager ThinServer when processing messages, allowing an unauthenticated remote attacker to upload arbitrary files to any directory on the disk where ThinServer.exe is installed. This can be exploited to overwrite existing executable files with malicious content, leading to 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>= 6.0.0, <= 10.0.2>= 11.0.0, <= 11.0.5>= 11.1.0, <= 11.1.5>= 11.2.0, <= 11.2.6>= 12.0.0, <= 12.0.4>= 12.1.0, <= 12.1.5= 13.0.0= 13.0.1CVSS 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 file, typically found in the ThinManager installation directory (commonly C:\Program Files\Rockwell Software\ThinManager or similar). Check Services snap-in or registry for the ThinServer service path.Affected if ThinServer.exe is present on the system in any location.
-
Identify ThinManager versionRight-click ThinServer.exe or ThinManager.exe, select Properties, and check the File Version or Product Version field. Alternatively, open ThinManager and navigate to Help > About to view the version.Affected if The installed version falls within any of these ranges: 6.0.0-10.0.2, 11.0.0-11.0.5, 11.1.0-11.1.5, 11.2.0-11.2.6, 12.0.0-12.0.4, 12.1.0-12.1.5, 13.0.0, or 13.1.1.
-
Verify ThinServer service statusOpen Services (services.msc), locate the ThinServer service, and check if its status is Running. Also note the startup type (Automatic, Manual, or Disabled).Affected if The ThinServer service is running or set to start automatically.
-
Assess network exposureReview firewall rules and network configuration to determine if ThinServer ports (default ThinManager port 2031/TCP, or configured port) are accessible from untrusted or external networks. Use netstat -an to list listening ports.Affected if ThinServer is listening on a port accessible from untrusted networks (e.g., not behind a properly segmented firewall).
The environment is affected if ThinServer.exe is installed and the version matches any of the vulnerable ranges listed, regardless of service status, since the path traversal flaw exists in the software itself.
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 · scopedApply vendor-provided patches immediately. If no patch is available, network segment ThinServer from untrusted networks and implement file-system monitoring to detect unauthorized file modifications.
ThinManager 11.2.7 or later
- 1. Identify the current ThinManager ThinServer version running in the environment
- 2. Navigate to Rockwell Automation's official support website (rockwellautomation.com) or the ThinManager product page
- 3. Locate and download ThinManager version 11.2.7 or later (or the latest available version)
- 4. Review the release notes for any specific upgrade instructions or prerequisites
- 5. Create a complete backup of the ThinManager configuration and any relevant system data
- 6. Test the upgrade in a non-production environment first to verify compatibility
- 7. Apply the upgrade to the production ThinManager ThinServer installation
- 8. Verify that ThinServer.exe is running the updated version and that all expected functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27855 — 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-27855 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