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

[R3] Nessus 6.10.5 Fixes Two Vulnerabilities



Nessus was found to be vulnerable to a local privilege escalation issue and a local denial of service condition 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. Note that these are very similar to, but different than the Agent issue fixed in version 6.10.4.

  • A local privilege escalation exists due to insecure permissions. CVSSv2 7.2 / 5.6 (AV:L/AC:L/Au:N/C:C/I:C/A:C/E:POC/RL:OF/RC:C). Tracked internally as NES-6137, CVE-2017-7850.
  • A local denial of service condition exists due to insecure permissions that would stop the agent from conducting scans. CVSSv2 2.1 / 1.7 (AV:L/AC:L/Au:N/C:N/I:N/A:P/E:F/RL:OF/RC:C). CVE-2017-7849


Tenable has released Nessus version 6.10.5 that corresponds to the supported operating systems and architectures. To update your Nessus installation, follow these steps:

Note that only agents are impacted by the local privilege escalation issue, 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.

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]