CVE-2025-9065
BaseFortify
Publication date: 2025-09-09
Last updated on: 2025-10-20
Assigner: Rockwell Automation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| rockwellautomation | thinmanager | From 13.0.0 (inc) to 14.0.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-610 | The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere. |
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-9065 is a Server-Side Request Forgery (SSRF) vulnerability in Rockwell Automation's ThinManager software (versions 13.0 through 14.0). Due to insufficient input sanitization, authenticated attackers can specify external SMB paths, which allows them to expose the ThinServer service account's NTLM hash. This can potentially compromise authentication credentials. [1]
How can this vulnerability impact me? :
Exploiting this vulnerability can expose the ThinServer service account's NTLM hash, which may allow attackers to compromise authentication credentials. This can lead to unauthorized access or further attacks within the affected environment. The vulnerability has a high severity rating with a CVSS 4.0 base score of 8.6, indicating significant potential impact. [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, immediately upgrade Rockwell Automation ThinManager software to version 14.1 or later where the issue is fixed. If upgrading is not possible right away, follow security best practices such as blocking NTLM connections over SMB as per Microsoft guidance for Windows Server 2025. Additionally, consider restricting authenticated access to ThinManager and monitor for any suspicious SMB path usage to reduce risk. [1]