dbcve.org
Thinmanager ThinserverApplication · Rockwellautomation

CVE-2023-2915

CRITICAL · 9.1 CVSS v3.1 Published 2023-08-17
Fix available
A fix is available. Upgrade to after 13.0.2 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
The Rockwell Automation Thinmanager Thinserver is impacted by an improper input validation vulnerability, Due to improper input validation, a path traversal vulnerability exists when the ThinManager software processes a certain function. If exploited, an unauthenticated remote threat actor can delete arbitrary files with system privileges. A malicious user could exploit this vulnerability by sending a specifically crafted synchronization protocol message resulting in a denial-of-service condition.

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

Rockwell Automation ThinManager Thinserver contains a path traversal vulnerability due to improper input validation in its synchronization protocol handling. An unauthenticated remote attacker can send specially crafted synchronization protocol messages to delete arbitrary files with system privileges or cause denial-of-service conditions.

MitigationApply vendor-supplied patches or updates for ThinManager Thinserver. Until patched, restrict network access to ThinManager services and implement network segmentation to limit exposure from unauthenticated remote attackers.

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
Thinmanager ThinserverApplication
Affected:>= 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.0

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

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

  1. Confirm ThinManager Thinserver installation
    Locate ThinManager Thinserver on the system using software inventory or installed programs listing
    Affected if ThinManager Thinserver is not found on the system, the system is not affected by this vulnerability
  2. Identify installed Thinserver version
    Use the ThinManager interface, registry, or product documentation to retrieve the Thinserver 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
  3. Verify synchronization protocol exposure
    Check ThinManager configuration settings or network listening services to determine if the synchronization protocol is enabled and accessible
    Affected if The synchronization protocol is enabled and accepts remote connections from untrusted networks
  4. Assess network accessibility
    Review firewall rules, network ACLs, or service bindings to determine if ThinManager Thinserver is reachable from unauthenticated remote attackers
    Affected if Thinserver is exposed to untrusted network segments or the internet without authentication or access controls

The system is affected if ThinManager Thinserver is installed with a version matching the affected ranges AND the synchronization protocol is accessible to unauthenticated remote attackers.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 13.0.2
Interim mitigation

Apply vendor-supplied patches or updates for ThinManager Thinserver. Until patched, restrict network access to ThinManager services and implement network segmentation to limit exposure from unauthenticated remote attackers.

Recommended fix Moderate confidence

Latest 11.0.7+, 11.1.7+, 11.2.8+, or 12.0.6+ (depending on your current major version branch)

  1. Identify the currently installed Thinmanager Thinserver version by checking the ThinManager administration interface or the installed software list
  2. Determine which version range your current installation falls into (11.0.x, 11.1.x, 11.2.x, or 12.0.x)
  3. Navigate to the Rockwell Automation ThinManager download page or contact Rockwell Automation technical support to obtain the latest version
  4. Download the appropriate updated version: For 11.0.x users, upgrade to 11.0.7 or later; For 11.1.x users, upgrade to 11.1.7 or later; For 11.2.x users, upgrade to 11.2.8 or later; For 12.0.x users, upgrade to 12.0.6 or later
  5. Before upgrading, backup the ThinManager configuration and any critical data
  6. Stop the ThinManager Thinserver service before performing the upgrade
  7. Install the new version following the standard ThinManager upgrade procedure
  8. Restart the ThinManager Thinserver service after installation
Caveat Standard upgrade precautions apply - backup configuration before upgrading; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Thinmanager Thinserver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-2915 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2915 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