CVE-2025-3618
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 denial-of-service vulnerability exists in the Rockwell Automation ThinManager. The software fails to adequately verify the outcome of memory allocation while processing Type 18 messages. If exploited, a threat actor could cause a denial-of-service on the target software.
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 denial-of-service vulnerability exists in Rockwell Automation ThinManager due to insufficient verification of memory allocation outcomes when processing Type 18 messages. A remote attacker could exploit this to cause the software to fail by triggering improper memory handling, resulting in service disruption.
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.2.11>= 12.0.0, < 12.0.9>= 12.1.0, < 12.1.10>= 13.0.0, < 13.0.7>= 13.1.0, < 13.1.5>= 13.2.0, < 13.2.4>= 14.0.0, < 14.0.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Confirm ThinManager installationLocate ThinManager on the system. Check common installation paths such as C:\Program Files\Rockwell Software\ThinManager or C:\Program Files (x86)\Rockwell Software\ThinManager. On Windows, open Programs and Features (appwiz.cpl) to list installed software and look for 'ThinManager'.Affected if ThinManager software is not found on the system, the user is not affected by this specific vulnerability.
-
Determine installed ThinManager versionRight-click the ThinManager application shortcut, select Properties, and view the Version tab. Alternatively, locate the ThinManager.exe file in the installation directory, right-click it, select Properties, and check the Details tab for version information.Affected if The installed version must be compared against the affected ranges: < 11.2.11, >= 12.0.0 to < 12.0.9, >= 12.1.0 to < 12.1.10, >= 13.0.0 to < 13.0.7, >= 13.1.0 to < 13.1.5, >= 13.2.0 to < 13.2.4, or >= 14.0.0 to < 14.0.2. If the version falls within any of these ranges, the system is potentially affe
-
Verify ThinManager network exposureCheck if ThinManager is listening on network ports. Open Command Prompt and run 'netstat -an | findstr LISTENING' to list listening ports. ThinManager typically uses ports 2031, 2041, or 6702 for ThinManager services. Also check Windows Firewall rules for ThinManager exceptions.Affected if If ThinManager is exposed to untrusted networks (internet-facing or accessible from less-trusted network segments) and the version is within the affected ranges, the vulnerability is more likely to be exploitable.
-
Review event logs for service disruptionsOpen Windows Event Viewer, navigate to Windows Logs > Application and System. Look for entries with source 'ThinManager' or keywords like 'Type 18', 'memory', 'crash', or 'service failure' around the time of any observed disruptions.Affected if If event logs show repeated crashes, service restarts, or memory-related errors associated with ThinManager, and the version is within affected ranges, this may indicate exploitation attempts.
The environment is affected if ThinManager is installed and the installed version falls within any of these vulnerable ranges: < 11.2.11, >= 12.0.0 to < 12.0.9, >= 12.1.0 to < 12.1.10, >= 13.0.0 to < 13.0.7, >= 13.1.0 to < 13.1.5, >= 13.2.0 to < 13.2.4, or >= 14.0.0 to < 14.0.2.
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.2.1112.0.912.1.10
Apply vendor-supplied patches or updates for ThinManager once available. Until then, consider network segmentation to limit exposure of ThinManager to untrusted networks and monitor for anomalous behavior.
11.2.11 (for v11.x), 12.0.9 (for v12.0.x), 12.1.10 (for v12.1.x), or 13.0.7 (for v13.x)
- Identify the current ThinManager version by checking the ThinManager software or system information
- Navigate to the Rockwell Automation download page or support portal for ThinManager
- Download the fixed version corresponding to your current major version branch: 11.2.11, 12.0.9, 12.1.10, or 13.0.7
- Review the Rockwell Automation upgrade instructions and release notes before proceeding
- Apply the upgrade following the standard ThinManager upgrade procedure, ensuring appropriate backup and maintenance window
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3618 — 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-2025-3618 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