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

[R1] SecurityCenter 5.6.0.1 Fixes Multiple Third-party Vulnerabilities

Medium

Synopsis

SecurityCenter leverages third-party software to help provide underlying functionality. Two of the third-party components (PHP and OpenSSL) were 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 PHP and OpenSSL to address the potential impact of these issues on SecurityCenter. SecurityCenter 5.6.0.1 updates PHP to version 5.6.32 and OpenSSL to version 1.0.2m to address the identified vulnerabilities.

References for the issues are below:
  • PCRE Library Heap Overflow Vulnerability (CVE-2016-1283)
  • OpenSSL Security Bypass Vulnerability (CVE-2017-3735)
  • OpenSSL Information Disclosure Vulnerability (CVE-2017-3736)

Note: The CVSSv2 score used in this advisory reflects CVE-2016-1283, as it is considered the highest risk.

Solution

Tenable has released SecurityCenter 5.6.0.1 to address these issues. The new version 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]