Synopsis
Nessus was found to be vulnerable to a local privilege escalation issue due to insecure permissions when running in Agent Mode. This may allow an attacker to gain administrative privileges on the system hosting a Nessus agent. This is tracked internally as NES-6023.
Solution
Tenable has released Nessus version 6.10.4 that corresponds to the supported operating systems and architectures. To update your Nessus installation, follow these steps:
- Download the appropriate installation file to the system hosting Nessus Professional or Nessus Manager, available at the Tenable Support Portal (https://support.tenable.com/support-center/index.php?x=&mod_id=200)
- Stop the Nessus service.
- Install according to your operating system procedures.
- Restart the Nessus service.
Note that only agents are impacted by this vulnerability, not scanners. If Nessus Manager is updated then auto updates will be deployed to the agents as well. If the agent is on Tenable.io then all of the agents will receive the updates.
Additional References
http://static.tenable.com/prod_docs/upgrade_nessus.html#6104https://aspe1337.blogspot.no/2017/03/upcoming-writeup-of-cve-2017-7199.html
https://aspe1337.blogspot.no/2017/04/writeup-of-cve-2017-7199.html
This page contains information regarding security vulnerabilities that may impact Tenable's products. This may include issues specific to our software, or due to the use of third-party libraries within our software. Tenable strongly encourages users to ensure that they upgrade or apply relevant patches in a timely manner.
Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.
For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.
If you have questions or corrections about this advisory, please email [email protected]