[R4] Nessus 6.5.5 Fixes Multiple Vulnerabilities

1 - CVE-2016-82000 - Two fields in the 'Host Details' section of a scan did not properly sanitize input. By importing a malicious file or scanning a compromised host returning JavaScript instead of a hostname, an attacker could introduce JavaScript that would be stored in the scan results, which could be in turn be executed within the context of the user viewing the results.

Note that this issue goes back to the Nessus UI version 2.0.0.

CVSSv2 Base/Temporal: 2.6 / 2.1 (AV:N/AC:H/Au:N/C:N/I:P/A:N/E:F/RL:OF/RC:C)

#2 - CVE-2016-82001 - When scanning a Mac OS X host using credentials, a malicious local user could trick Nessus into executing an arbitrary command as root, thus resulting into a privilege-escalation vulnerability.

Note that the following CVSSv2 score reflects the risk to the host being scanned by Nessus, not the system hosting Nessus. Since Nessus is being used as an exploit for a target host, the score does not reflect a threat to Nessus. As such, it is not being listed as the primary CVSSv2 score for this advisory.

CVSSv2 Base/Temporal: 7.6 / 4.9 (AV:N/AC:H/Au:N/C:C/I:C/A:C/E:POC/RL:OF/RC:C)

#3 Nessus Folder Name Stored Scripting

Charlie Svensson reported that Nessus will render script code for folder names. This was also found internally but filed as a regular bug, as the folder names only render to the user who renamed them. Since folder names are not seen across user accounts, this does not pose any risk. Regardless, this issue has been fixed.

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