Nessus Network Monitor vulnerabilities
5 known vulnerabilities in Nessus Network Monitor from Tenable. 5 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 7.8 High severity
Network Monitor: Improper Access Control
In Tenable Network Monitor versions prior to 6.5.1 on a Windows host, it was found that a non-administrative user could stage files in a local directory to run arbitrary code with SYSTEM privileges, potentially leading to local privilege escalation.
- 7.8 High severity
Network Monitor: Improper Access Control
When installing Tenable Network Monitor to a non-default location on a Windows host, Tenable Network Monitor versions prior to 6.5.1 did not enforce secure permissions for sub-directories. This could allow for local privilege escalation if users had not secure
- 7.2 High severity
Under certain conditions, Nessus Network Monitor was found to not properly enforce input…
Under certain conditions, Nessus Network Monitor was found to not properly enforce input validation. This could allow an admin user to alter parameters that could potentially allow a blindSQL injection.
- 7.8 High severity
Nessus Network Monitor: Improper Control of Generation of Code
NNM failed to properly set ACLs on its installation directory, which could allow a low privileged user to run arbitrary code with SYSTEM privileges where NNM is installed to a non-standard location
- 8.8 High severity
Nessus Network Monitor: Improper Privilege Management
Under certain conditions, Nessus Network Monitor could allow a low privileged user to escalate privileges to NT AUTHORITY\SYSTEM on Windows hosts by replacing a specially crafted file.