Synopsis
Out of caution and in line with good practice, Tenable opted to upgrade the bundled libraries to address the potential impact of these issues in SecurityCenter. SecurityCenter 5.8.0 updates both Apache Xalan and Serializer to version 2.7.2 to address the identified vulnerabilities. A separate stand-alone patch (SecurityCenter Patch 201811.1) has also been released to address these issues for customers running SecurityCenter 5.7.1 and earlier.
Note: The CVSSv2 score used in this advisory reflects CVE-2014-0107, as it is considered the highest risk.
Solution
Tenable has released SecurityCenter 5.8.0 and SecurityCenter Patch 201811.1 to address these issues. The installation files can be obtained from the Tenable Downloads Portal (https://www.tenable.com/downloads/securitycenter-3d-tool-and-xtool).Note: If you are running SecurityCenter version 5.5.0 or later, you can upgrade directly to version 5.8.0. If you are running a version earlier than 5.5.0, upgrade to version 5.5.0 before upgrading to version 5.8.0.
Note: If you are running SecurityCenter version 5.7.1 or earlier, you can apply the stand-alone patch without upgrading to SecurityCenter 5.8.0. Instructions to apply the stand-alone patch can be obtained from the SecurityCenter 201811.1 Release Notes page (https://docs.tenable.com/releasenotes/securitycenter/securitycenter_20181113.htm).
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]