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

[R3] SecurityCenter 4.8.2 Fixes Third-party Library Vulnerability



SecurityCenter is impacted by one vulnerability in PHP that was recently disclosed and fixed.

CVE-2014-3669: PHP contains an integer overflow condition in the object_custom() function in ext/standard/var_unserializer.re that is triggered when serializing user-supplied input. With specially crafted input, a remote attacker can cause a crash.

Note that this vulnerability only impacts 32-bit versions. Customers who use the 64-bit version are not affected.

In addition to the issue above, two additional vulnerabilities were patched by the PHP team. SecurityCenter does not use the module related to the XMLRPC calls (CVE-2014-3668) so it is not affected. SecurityCenter also does not use the exif_thumbnail function (CVE-2014-3670) so it is not affected by this either.

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


Tenable has released SecurityCenter 4.8.2 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]