CVE-2024-5989
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 · uneditedDue to an improper input validation, an unauthenticated threat actor can send a malicious message to invoke SQL injection into the program 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 · high confidenceA critical improper input validation vulnerability in Rockwell Automation ThinManager ThinServer allows unauthenticated remote attackers to inject malicious SQL commands via specially crafted messages. This SQL injection can be leveraged to achieve remote code execution on the affected ThinServer component.
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.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>= 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.2CVSS 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.
-
Identify if ThinManager or ThinServer is installedCheck for ThinManager installation directory (typically C:\Program Files\Rockwell Software\ThinManager or C:\ThinManager) or look for ThinServer service in Windows Services (look for 'ThinServer' or 'ThinManager' service)Affected if Either ThinManager or ThinServer software is present on the system
-
Determine the installed ThinManager versionOpen Windows Control Panel > Programs and Features, locate 'Rockwell Automation ThinManager' and note the version column, or right-click ThinManager.exe and view Properties > Details > File VersionAffected if Version falls within 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
-
Determine the installed ThinServer versionCheck the ThinServer executable version: locate ThinServer.exe in the installation directory, right-click and view Properties > Details > File Version, or run 'wmic product where "name like 'ThinServer'" get version' if availableAffected if Version falls within any of the affected version ranges listed above
-
Verify ThinServer network exposureOpen Windows Firewall with Advanced Security > Inbound Rules and look for rules allowing traffic on ports used by ThinServer (typically port 2031/TCP or configurable ports). Use 'netstat -an | findstr LISTENING' to identify listening ports associated with ThinServer processAffected if ThinServer is listening on accessible network ports and accepts remote connections
-
Check for suspicious SQL-related log entriesLocate ThinManager logs (typically in C:\ProgramData\ThinManager\Logs or installation logs folder) and search for SQL errors, unusual database queries, or injection attempt patterns using 'type *.log | findstr /i "sql select insert"'Affected if Logs contain unexpected SQL syntax, database errors, or evidence of injection attempts
You are affected if ThinManager or ThinServer is installed and the version falls within any of the affected version ranges AND the ThinServer component 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.
dbcve · scoped11.1.811.2.912.0.7
Apply vendor-released patches immediately, restrict network access to ThinManager ThinServer to minimize exposure, and implement network segmentation to isolate industrial control system components.
Upgrade to ThinManager/ThinServer version 11.1.8+, 11.2.9+, 12.0.7+, or 12.1.8+ (depending on your current major version branch)
- 1. Identify the current installed version of ThinManager or ThinServer by checking the application properties or about dialog
- 2. Based on your current major version (11.1.x, 11.2.x, 12.0.x, or 12.1.x), plan an upgrade to the respective minimum fixed version
- 3. For version 11.1.x: upgrade to version 11.1.8 or later
- 4. For version 11.2.x: upgrade to version 11.2.9 or later
- 5. For version 12.0.x: upgrade to version 12.0.7 or later
- 6. For version 12.1.x: upgrade to version 12.1.8 or later
- 7. Download the appropriate updated version from the official Rockwell Automation website
- 8. Before installing in production, test the upgrade in a non-production environment to verify compatibility
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.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,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5989 — 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-2024-5989 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