CVE-2024-7986
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 vulnerability exists in the Rockwell Automation ThinManager® ThinServer that allows a threat actor to disclose sensitive information. A threat actor can exploit this vulnerability by abusing the ThinServer™ service to read arbitrary files by creating a junction that points to the target directory.
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 and arbitrary file read vulnerability in Rockwell Automation ThinManager ThinServer allows authenticated or local attackers to read sensitive files by creating Windows filesystem junctions that point to target directories, bypassing intended access 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Confirm ThinManager ThinServer is installedOpen Windows Services (services.msc) and look for a service named 'ThinManager ThinServer' or check Program Files for ThinManager installation directoryAffected if The ThinManager ThinServer service or software is present on the system
-
Identify the installed ThinManager versionCheck the ThinManager version via the ThinManager application UI (Help > About) or look in the registry under HKLM\SOFTWARE\Rockwell Software\ThinManager or check the installation directory for version informationAffected if The installed version falls within any of the affected 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
-
Verify ThinServer service is runningIn Services console, check if the 'ThinManager ThinServer' service status is 'Running', or run 'sc query ThinServer' from command promptAffected if The ThinServer service is currently running and exposed to authenticated or local users
-
Audit for suspicious filesystem junctionsUse 'dir /AL /S C:\' or 'Get-ChildItem -Path C:\ -Recurse -Directory -Filter * -Force | Where-Object { $_.LinkType -eq "Junction" }' to list all junction points on the system, particularly in ThinManager data directoriesAffected if New or unexpected junction points exist that point to sensitive directories outside normal ThinManager paths
-
Review ThinServer logs for path traversal attemptsLocate ThinManager log files (typically in the ThinManager installation/logs folder or Windows Event Viewer under Application logs) and search for unusual file access patterns, '..' path sequences, or access to system files outside the intended directoryAffected if Log entries show path traversal patterns or unauthorized file access attempts
You are affected if ThinManager ThinServer is installed with a version matching the affected ranges AND the ThinServer service is running, allowing authenticated or local users to potentially exploit the path traversal via filesystem junctions.
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 patches for ThinManager ThinServer; implement least-privilege access controls and network segmentation to limit exposure to the ThinServer service.
11.1.8, 11.2.9, 12.0.7, or 12.1.8 (depending on current version branch)
- Identify the current ThinManager version by checking the ThinManager application or Windows Programs and Features
- Determine which version branch you are on (11.1.x, 11.2.x, 12.0.x, or 12.1.x)
- Review release notes for the target fixed version to understand any changes
- Back up the ThinManager configuration and any relevant data
- Download the appropriate fixed version from the Rockwell Automation website or support portal
- Stop the ThinManager ThinServer service before upgrading
- Install the fixed version (11.1.8, 11.2.9, 12.0.7, or 12.1.8 depending on your branch)
- Start the ThinManager ThinServer service after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7986 — 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-7986 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