CVE-2024-5990
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 a monitor thread within Rockwell Automation ThinServer™ and cause a denial-of-service condition on the affected device.
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 confidenceThis vulnerability in Rockwell Automation ThinServer™ stems from improper input validation that allows unauthenticated attackers to send malicious messages directly to a monitor thread. The attack requires no authentication and specifically targets the monitor thread functionality, causing a denial-of-service condition on the affected device.
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.4>= 13.1.0, < 13.1.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.4>= 13.1.0, < 13.1.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify if ThinManager or ThinServer is installedCheck for ThinManager or ThinServer in Windows installed programs. Open Control Panel > Programs and Features, or run PowerShell: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Select-Object DisplayName | Where-Object {$_.DisplayName -match 'ThinManager|ThinServer'}Affected if Neither ThinManager nor ThinServer is found in the installed programs list, then not affected
-
Determine the installed versionOpen ThinManager or ThinServer and navigate to Help > About to view the version number. Alternatively, check the Windows registry at HKLM:\SOFTWARE\Rockwell Software\ThinManager\CurrentVersion for the Version valueAffected if Unable to retrieve version information from the software or registry
-
Compare against affected version rangesMatch the installed version number against the vulnerable 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.4; >= 13.1.0 and < 13.1.2Affected if Installed version falls within any of these version ranges
-
Check monitor thread network exposureReview network configuration to determine if the ThinServer monitor thread interface is accessible from the network. Check firewall rules and network segmentation for port 2045 (default ThinServer port) or any port ThinServer is listening onAffected if The ThinServer monitor thread is exposed to untrusted network segments without proper access controls
-
Verify if ThinServer service is runningOpen Windows Services console (services.msc) and check if the ThinServer service or ThinManager service is running, or run Get-Service | Where-Object {$_.Name -match 'ThinServer|ThinManager'}Affected if ThinServer or ThinManager service is not running
You are affected if ThinManager or ThinServer is installed with a version matching any of the vulnerable ranges AND the monitor thread functionality is network-accessible to unauthenticated attackers.
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 available vendor patches for ThinServer™ and implement network segmentation to restrict unauthorized access to the ThinServer interface.
Upgrade to 11.1.8, 11.2.9, 12.0.7, or 12.1.8 depending on your current version branch
- Identify currently installed ThinManager or Thinserver version by checking About or version information in the product
- Determine which version branch you are on (11.1.x, 11.2.x, 12.0.x, or 12.1.x)
- For version 11.1.x: upgrade to version 11.1.8
- For version 11.2.x: upgrade to version 11.2.9
- For version 12.0.x: upgrade to version 12.0.7
- For version 12.1.x: upgrade to version 12.1.8
- Download the appropriate fixed version from the Rockwell Automation website or support portal
- Apply the upgrade following standard ThinManager/Thinserver upgrade procedures
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5990 — 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-5990 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