dbcve.org
ThinmanagerApplication · Rockwellautomation

CVE-2024-5988

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-25
Fix available
A fix is available. Upgrade to 11.1.8 / 11.2.9 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Due to an improper input validation, an unauthenticated threat actor can send a malicious message to invoke a local or remote executable and cause a remote code execution condition on the Rockwell Automation ThinManager® ThinServer™.

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 confidence

The vulnerability exists in Rockwell Automation ThinManager ThinServer due to improper input validation. An unauthenticated attacker can send specially crafted malicious messages that bypass input checks and trigger execution of local or remote executables, leading to remote code execution on the affected system.

MitigationApply vendor patches immediately and restrict network access to ThinServer to only trusted sources. If patching is not immediately feasible, implement network segmentation and monitor for suspicious messages to the ThinServer service.

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
ThinmanagerApplication
Affected:>= 11.1.0, < 11.1.8>= 11.2.0, < 11.2.9>= 12.0.0, < 12.0.7>= 12.1.0, < 12.1.8>= 13.0.0, < 13.0.5>= 13.1.0, < 13.1.3>= 13.2.0, < 13.2.2
ThinserverApplication
Affected:>= 11.1.0, < 11.1.8>= 11.2.0, < 11.2.9>= 12.0.0, < 12.0.7>= 12.1.0, < 12.1.8>= 13.0.0, < 13.0.5>= 13.1.0, < 13.1.3>= 13.2.0, < 13.2.2

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

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

  1. Identify if ThinManager or ThinServer is installed
    Check Windows installed programs list or registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'ThinManager' or 'ThinServer'. Alternatively, check Program Files for ThinManager installation directory.
    Affected if The software is present on the system
  2. Determine installed version of ThinManager or ThinServer
    Open ThinManager and go to Help > About, or check the file properties of ThinServer.exe typically located in C:\Program Files\Rockwell Software\ThinManager\, or check the version in Add/Remove Programs.
    Affected if Version matches any of these ranges: >= 11.1.0 and < 11.1.8; >= 11.2.0 and < 11.2.9; >= 12.0.0 and < 12.0.7; >= 12.1.0 and < 12.1.8; >= 13.0.0 and < 13.0.5; >= 13.1.0 and < 13.1.3; >= 13.2.0 and < 13.2.2
  3. Verify ThinServer service is running
    Open Services.msc and locate 'ThinServer' service, or run 'sc query ThinServer' from command prompt. Check if the service status is Running.
    Affected if The ThinServer service is running and accessible on the network
  4. Check network exposure of ThinServer
    Run 'netstat -an | findstr LISTENING' to see which ports ThinServer is listening on. By default ThinServer uses port 2031. Verify if this port is bound to external IPs or firewall rules allow external access.
    Affected if ThinServer port is exposed to untrusted network segments or the internet

The system is affected if ThinManager or ThinServer is installed with a version falling within any of the listed vulnerable ranges AND the ThinServer service is network-accessible.

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 11.1.8 / 11.2.9 / 12.0.7 or later
Fixed in 11.1.811.2.912.0.7
Interim mitigation

Apply vendor patches immediately and restrict network access to ThinServer to only trusted sources. If patching is not immediately feasible, implement network segmentation and monitor for suspicious messages to the ThinServer service.

Recommended fix High confidence

Upgrade to ThinManager ThinServer version 11.1.8, 11.2.9, 12.0.7, or 12.1.8 (or later) depending on your current branch

  1. 1. Identify the current installed version of ThinManager ThinServer by checking the application or system information
  2. 2. Determine which version branch is currently in use (11.1.x, 11.2.x, 12.0.x, or 12.1.x)
  3. 3. Access the Rockwell Automation website or support portal to download the appropriate fixed version
  4. 4. For branch 11.1.x: upgrade to version 11.1.8 or later
  5. 5. For branch 11.2.x: upgrade to version 11.2.9 or later
  6. 6. For branch 12.0.x: upgrade to version 12.0.7 or later
  7. 7. For branch 12.1.x: upgrade to version 12.1.8 or later
  8. 8. Test the upgrade in a non-production environment before deploying to production

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

Fix this in Thinmanager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5988 — 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-2024-5988 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