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

[R5] Nessus 5.0 Fixes Third-party Library Vulnerability

Medium

Synopsis

Tenable's Nessus scanner is affected by a vulnerability in the bundled version of the OpenSSL library. The issue is triggered when a malicious client requests multiple SSL/TLS renegotations, and will result in a temporary loss of availability for the web service.

Solution

Tenable has updated the product to address this issue. Please see the instructions below:

Tenable has released Nessus version 5.0 that corresponds to the supported operating systems and architectures. This version bundles an updated OpenSSL library which is not affected.

To update your Nessus installation, follow these steps:

  1. Download the appropriate installation file to the system hosting Nessus or Nessus Enterprise, available at the Tenable Support Portal (https://support.tenable.com/support-center/index.php?x=&mod_id=200)
  2. Stop the Nessus service.
  3. Install according to your operating system procedures.
  4. Restart the Nessus service.

In addition, Tenable has authored a Nessus Plugin (ID 53491, ssl_renegotiation_dos.nasl) that detects this TLS/SSL vulnerability.

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]