CVE-2025-9267
BaseFortify
Publication date: 2025-09-26
Last updated on: 2025-09-29
Assigner: Seagate Technology
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| seagate | seagate_toolkit | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-426 | The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control. |
| CWE-427 | The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Seagate Toolkit Installer on Windows versions prior to 2.35.0.6. The installer attempts to load DLL files from the current working directory without verifying their origin or integrity. An attacker can exploit this by placing a malicious DLL in the same directory as the installer executable, causing the installer to load and execute the malicious code with the privileges of the user running the installer. The root cause is insecure DLL loading practices, such as using relative paths or not specifying fully qualified paths for system libraries.
How can this vulnerability impact me? :
This vulnerability can lead to arbitrary code execution with the privileges of the user running the installer. If exploited, an attacker could execute malicious code on the affected system, potentially leading to unauthorized actions, data compromise, or system manipulation depending on the user's privileges.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Seagate Toolkit Installer to version 2.35.0.6 or later. Avoid running the installer from directories that may contain untrusted DLLs. Ensure that the installer is executed from a trusted location and consider running it with the least privileges necessary to reduce risk.