CVE-2025-34078
BaseFortify
Publication date: 2025-07-02
Last updated on: 2025-11-25
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| nsclient | nsclient\+\+ | 0.5.2.35 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-312 | The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. |
| CWE-522 | The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. |
| CWE-269 | The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in NSClient++ version 0.5.2.35 when both the web interface and ExternalScripts features are enabled. The administrative password is stored in plaintext in the configuration file (nsclient.ini), which local users can read. An attacker with low privileges can extract this password, authenticate to the NSClient++ web interface, and abuse the ExternalScripts plugin to register and execute arbitrary commands as the SYSTEM user. This allows the attacker to escalate their privileges from a low-privileged user to full system control. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow a local attacker with low privileges to gain SYSTEM-level access on the affected Windows system. By extracting the plaintext administrative password, the attacker can log into the NSClient++ web interface, enable modules to run arbitrary scripts, upload malicious scripts, and execute them with the highest system privileges. This leads to full control over the system, bypassing authentication and privilege restrictions, and potentially compromising the entire host. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if NSClient++ version 0.5.2.35 is installed with both the web interface and ExternalScripts features enabled. You can verify if the nsclient.ini configuration file is accessible and contains the web administrator password in plaintext. On the system, you can inspect the file at the default path (e.g., C:\Program Files\NSClient++\nsclient.ini) for readable plaintext passwords. Additionally, you can check if the NSClient++ web interface is accessible on port 8443. Commands to check the file permissions and contents could include: 1) On Windows, use 'icacls "C:\Program Files\NSClient++\nsclient.ini"' to check permissions. 2) Use 'type "C:\Program Files\NSClient++\nsclient.ini"' or open it in a text editor to look for plaintext passwords. 3) Use 'netstat -an | findstr 8443' to check if the web interface port is listening. 4) Use a web request tool (e.g., curl or a browser) to test access to https://localhost:8443. These steps help identify if the vulnerable configuration is present and accessible. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Disable either the web interface or the ExternalScripts feature in NSClient++ to prevent exploitation. 2) Restrict access permissions to the nsclient.ini configuration file to prevent local users from reading the plaintext administrative password. 3) Change the administrative password to a strong value and avoid storing it in plaintext if possible. 4) Apply any available patches or updates from the NSClient++ project that address this vulnerability. 5) If possible, restrict local user access to the system to trusted users only. 6) Consider disabling or limiting the use of the ExternalScripts plugin to reduce attack surface. 7) Monitor for suspicious activity related to NSClient++ web interface usage and script execution. 8) Reboot the system after configuration changes to ensure settings are applied properly. [1, 2]