Facebook Google Plus Twitter LinkedIn YouTube RSS Menu Search Resource - BlogResource - WebinarResource - ReportResource - Eventicons_066 icons_067icons_068icons_069icons_070

[R4] Nessus 6.9.3 Fixes Two Vulnerabilities



Tenable Nessus was found to be impacted by two authenticated stored cross-site scripting (XSS) issues.

The first was via a report from Asif Balasinor, covered a reflected XSS issue that was deemed to have no risk as it could only be triggered by the authenticated user. While evaluating that report the director of the Nessus development team, Nicolas Pouvesle, discovered a different stored XSS issue. Both of these have been fixed, but only the stored XSS posed a risk. Tenable thanks Asif Balasinor for his report and prompting us to look further. (CVE-2017-5179)

The second, a stored XSS issue that requires authentication was reported to JVN/JPCERT by Toshitsugu Yoneyama. (CVE-2017-2122)

Please note that Tenable strongly recommends that Nessus be installed on a subnet that is not Internet addressable.


Tenable has released Nessus version 6.9.3 that corresponds to the supported operating systems and architectures. This version addresses the XSS issues.

To update your Nessus installation, follow these steps:

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]