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

[R6] SecurityCenter Affected by Multiple Third-party Library Vulnerabilities

High

Synopsis

Tenable's SecurityCenter is affected by several vulnerabilities due to the use of third-party libraries, specifically Apache HTTP Server and PHP.

CVE-2014-3515 - PHP unserialize() Call SPL ArrayObject / SPLObjectStorage Type Confusion Remote Code Execution

PHP contains an type confusion flaw that is triggered when performing an unserialize() call to SPL ArrayObject or SPLObjectStorage in the SPL component. This may allow a remote attacker with the ability to pass data to these handlers to cause a denial of service or potentially execute arbitrary code.

Note that you must be logged in with a SecurityCenter user account and authenticated with proper privileges in order to leverage the API in a fashion to exploit this vulnerability.

Also note that additional PHP vulnerabilities affiliated with the two listed above do not affect SecurityCenter. These include CVE-2014-0207, CVE-2014-3478, CVE-2014-3479, CVE-2014-3480, CVE-2014-3487, CVE-2014-3981, CVE-2014-4049, and CVE-2014-3981.

CVE-2014-0098 - Apache HTTP Server mod_log_config Module mod_log_config.c log_cookie Function Malformed Cookie Handling Remote DoS

Apache HTTP Server contains a flaw in the mod_log_config module that is triggered when logging a cookie with an unassigned value. With a specially crafted request, a remote attacker can cause the service to crash.

Note that the CVSSv2 score reflects CVE-2014-0098, the highest of the two. Further, Tenable strongly recommends that SecurityCenter and the Appliance be installed on a subnet that is not Internet addressable.

Originally, we reported that SecurityCenter was vulnerable to CVE-2014-4049 due to a cursory analysis. Subsequent examination indicates that it is not affected

Solution

Tenable has created patches to address these issues. Please see the vulnerability-specific instructions below.

SecurityCenter

For CVE-2014-0098 (Apache HTTP Server), patches are provided for SC 4.8.1, SC 4.7.1, and SC 4.6.2.2. The SecurityCenter 4.8.1 patch also fixes CVE-2014-3515 (PHP).

Customers with SecurityCenter 4.6.x and 4.7.x that wish to apply a patch for the PHP related vulnerability can upgrade to SecurityCenter 4.8.1 and apply the patch mentioned above.

Note that this patch will re-apply the patches for OpenSSL as noted in TNS-2014-02 and TNS-2014-03.

The patch can be obtained from:

https://support.tenable.com/support-center/index.php?x=&mod_id=160

  1. Download the appropriate patch to the system hosting SecurityCenter. Files are named --.tgz. We recommend you put it in /tmp or its own folder.

  2. Untar the patch archive: # tar zxf ./--.tgz

  3. Run the install script: # ./install.sh

SecurityCenter 4.8.1 patches:

File                        md5sum
sc4.8.1-rh6-64.tgz          4ad4fb7bee4546d4c3a59b3ae3da39a6
sc4.8.1-rh6-32.tgz          7a9b66ac070bb322d9eb9127beedab57
sc4.8.1-rh5-64.tgz          003fd53de9d56568d3c29e08c93bcb90
sc4.8.1-rh5-32.tgz          639d867aee00d05f10d71c35ea5683bc

SecurityCenter 4.7.1 patches:

File                        md5sum
sc4.7.1-rh6-64.tgz          0c23ec8403b4f865953eb5aca6248f16
sc4.7.1-rh6-32.tgz          31e802c05658d9e363174cdaca5461ac
sc4.7.1-rh5-64.tgz          d88d8e5842122da166fcb45ccda01233
sc4.7.1-rh5-32.tgz          3e9f009924e692aeae0e795c74b17a2f

SecurityCenter 4.6.2.2 patches:

File                            md5sum
sc4.6.2.2-rh6-64.tgz            4df5e9904c58a881fa01ca5ac6c52dde
sc4.6.2.2-rh6-32.tgz            c014d0258a8af365e5cd609741ea8aab
sc4.6.2.2-rh5-64.tgz            fd160d7edb47a00a015624048b941583
sc4.6.2.2-rh5-32.tgz            ca22c43ca32b9bc6698c3cc2300ef8f7

Tenable Appliance

Appliance users can apply a patch that has been created for SecurityCenter 4.6.2.2, 4.7.1, or 4.8.1 running on it. When applied to an appliance running SecurityCenter 4.8.1, the vulnerabilities identified as CVE-2014-0098 (Apache HTTP Server) and CVE-2014-4049 (PHP) will be patched. When applied to an appliance running SecurityCenter 4.7.1 or SecurityCenter 4.6.2.2, the vulnerability for CVE-2014-0098 (Apache HTTP Server) will be patched.

If a user running SecurityCenter 4.6.x or 4.7.x wants to address the PHP vulnerability, they will need to upgrade to an appliance running SecurityCenter 4.8.1.

In addition, please note that this patch will re-apply the patches for OpenSSL as noted in TNS-2014-02 and TNS-2014-03 for SecurityCenter 4.6.2.2, 4.7.1, and 4.8.1.

The patch can be obtained from:

https://support.tenable.com/support-center/index.php?x=&mod_id=230

Tenable Appliance versions 2.4.1, 2.4.1-1, 2.6.0, 2.6.1, 2.6.2, and 2.8.1 require the following patch:

File                            md5sum

SC4-ApacheUpgrade.tar.gz        3dd17e456d34326050d501dac02d4eda

Tenable has also released version 3.0.0 of the appliance which resolves this issue.

File                                        md5sum                                    SHA1 sum
TenableAppliance-3.0.0-64-update.tar        3830a586afa9f0fb4c70f1cfb119f839          2384da2a29ec860782c3cfd168334ed19b59bf4a
TenableAppliance-HyperV-3.0.0-64bit.zip     86911ed30f657b5ea5d19b529bae0610          3fb28fbafa611e2279e2d5f1b894de770c088453
TenableAppliance-VMware-3.0.0-64bit.ova     5fbb61a26a39b89e2024fe617a8e8d99          2f5bbf2d694d56f880bae328d58ca81c5c48a13a

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]