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

[R2] SecurityCenter 5.6.1 Fixes Multiple Third-party Vulnerabilities

Medium

Synopsis

SecurityCenter leverages third-party software to help provide underlying functionality. One of the third-party components (OpenSSL) was found to contain vulnerabilities, and updated versions have been made available by the providers.

Out of caution and in line with good practice, Tenable opted to upgrade the bundled OpenSSL to address the potential impact of these issues in SecurityCenter. SecurityCenter 5.6.1 updates OpenSSL to version 1.0.2n to address the identified vulnerabilities.

Note: A separate patch has also been released to update OpenSSL to 1.0.2n in SecurityCenter versions 5.4.x, 5.5.x, and 5.6.0.x.

References for the issues are below:
  • OpenSSL security-bypass vulnerability (CVE-2017-3737)
  • OpenSSL information-disclosure vulnerability (CVE-2017-3738)

Solution

Tenable has released SecurityCenter 5.6.1 to address these issues. Also, a separate patch to only upgrade OpenSSL has been made available for users of SecurityCenter versions 5.4.x, 5.5.x, and 5.6.0.x. The update and OpenSSL patch can be obtained from the Tenable Support Portal (https://support.tenable.com/support-center/index.php?x=&mod_id=160).

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]