CVE-2025-8614
BaseFortify
Publication date: 2025-09-02
Last updated on: 2025-09-10
Assigner: Zero Day Initiative
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| nomachine | nomachine | to 8.17.2 (exc) |
| nomachine | nomachine | From 9.0 (inc) to 9.1.24 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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?
CVE-2025-8614 is a local privilege escalation vulnerability in NoMachine products caused by the software loading an OpenSSL configuration file from an unsecured location. This allows a local attacker who already has low-privileged code execution on the system to escalate their privileges by executing arbitrary code with the service account's privileges. [1]
How can this vulnerability impact me? :
This vulnerability can allow an attacker with limited access to escalate their privileges on the affected system, potentially gaining control over the service account running NoMachine. This could lead to unauthorized code execution, data compromise, or further system compromise. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by verifying if the NoMachine installation loads the OpenSSL configuration file from an unsecured or unexpected location. Checking the file paths and permissions of the OpenSSL configuration files used by NoMachine can help identify the issue. Specific commands to inspect the OpenSSL configuration file location and permissions include: 1) Using 'ps aux | grep nxserver' to identify the NoMachine service process and its environment. 2) Checking the OpenSSL configuration file path used by NoMachine, for example by examining environment variables or configuration files related to NoMachine. 3) Using 'ls -l' on the OpenSSL configuration file path to verify if it is in an unsecured location or writable by low-privileged users. However, no explicit detection commands are provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying the update released by NoMachine that addresses and fixes this vulnerability. Additionally, restricting access and permissions to the OpenSSL configuration files used by NoMachine to prevent unauthorized modification can help mitigate the risk. Ensuring that only trusted users have the ability to execute code on the system will also reduce the likelihood of exploitation. [1]