CVE-2024-7987
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 · uneditedA remote code execution vulnerability exists in the Rockwell Automation ThinManager® ThinServer™ that allows a threat actor to execute arbitrary code with System privileges. To exploit this vulnerability and a threat actor must abuse the ThinServer™ service by creating a junction and use it to upload arbitrary files.
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 confidenceA remote code execution vulnerability in Rockwell Automation ThinManager ThinServer allows authenticated or unauthenticated threat actors to execute arbitrary code with System privileges by creating a filesystem junction and leveraging it to upload malicious files, bypassing security restrictions.
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.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Verify ThinManager ThinServer is installedCheck for ThinManager installation directory (typically C:\Program Files\Rockwell Software\ThinManager\ or C:\ThinManager\) and look for ThinServer.exeAffected if ThinServer.exe exists on the system
-
Determine installed ThinServer versionRight-click ThinServer.exe, select Properties, then view the Details tab for File Version. Alternatively, run: powershell (Get-Item 'C:\Program Files\Rockwell Software\ThinManager\ThinServer.exe').VersionInfoAffected if Version falls within any of these ranges: 11.1.0-11.1.7, 11.2.0-11.2.8, 12.0.0-12.0.6, 12.1.0-12.1.7, 13.0.0-13.0.4, 13.1.0-13.1.2, or 13.2.0-13.2.1
-
Confirm ThinServer service is runningOpen Services console (services.msc) and locate 'ThinManager ThinServer' service, or run: Get-Service -Name 'ThinManager*' or Get-Process -Name ThinServerAffected if ThinServer service is in Running state and ThinServer.exe process is active
-
Check network exposure of ThinServer portsRun netstat -ano | findstr LISTENING to identify ports ThinServer is listening on (typically port 2031/2032 for ThinServer). Verify if these ports are exposed to untrusted networksAffected if ThinServer ports are listening on interfaces accessible from untrusted networks (0.0.0.0 or external IPs)
-
Audit for suspicious filesystem junctionsUse 'junction C:\ThinManager\config' or Sysinternals Junction utility to scan ThinManager directories for unexpected junction points, particularly in the config or protocol foldersAffected if Unexpected junctions exist in ThinManager installation directories, indicating potential exploitation artifacts
If ThinManager ThinServer is installed with a version in the affected ranges and the service is running with network exposure, the environment is vulnerable to CVE-2024-7987
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-provided security patches for ThinManager ThinServer, ensure the service runs with least privilege, and restrict network access to ThinServer ports.
Upgrade to 11.1.8, 11.2.9, 12.0.7, or 12.1.8 depending on your current version branch
- 1. Identify your current ThinManager ThinServer version from the ThinManager installation or the ThinManager Login dialog.
- 2. Based on your current version branch, upgrade to the corresponding fixed version: For 11.1.x branch, upgrade to 11.1.8; For 11.2.x branch, upgrade to 11.2.9; For 12.0.x branch, upgrade to 12.0.7; For 12.1.x branch, upgrade to 12.1.8.
- 3. Obtain the upgrade from the official Rockwell Automation website or your authorized Rockwell distributor.
- 4. Before upgrading, ensure you have a complete backup of your ThinManager configuration and relevant data.
- 5. Apply the upgrade following standard Rockwell Automation upgrade procedures for ThinManager.
- 6. After upgrade, verify that ThinServer service starts correctly and ThinManager functionality is intact.
- 7. Review ThinManager logs to confirm normal operation post-upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation12.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7987 — 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-7987 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