Synopsis
SecurityCenter is vulnerable to the recently disclosed OpenSSL 'Heartbleed' vulnerability as it bundles the software. The flaw in OpenSSL is due to an out-of-bounds read flaw that is triggered during the handling of TLS heartbeat extensions. This may allow a remote unauthenticated attacker to disclose up to 64k of memory at a time, that can contain sensitive information including secret keys, which would allow decryption of all traffic to and from the server. This affects the HTTPS web interface of SecurityCenter.
Note that while the CVSS score is 5.0 (Medium), it typically leads to a considerably more severe impact. Further, Tenable strongly recommends that SecurityCenter and the Tenable Appliance be installed on a subnet that is not Internet addressable.
Solution
Tenable has created four archives and they correspond to the supported operating systems and architectures. Each archive contains an updated .so file and an install script that will upgrade OpenSSL to 1.0.1h, which is not affected.
To apply the appropriate patch, follow these steps:
- Download the appropriate patch to the system hosting SecurityCenter. Files are named OpenSSL-patch-
- .tgz. We recommend you put it in /tmp or its own folder. - Untar the patch archive, for example: # tar zxf sc4.7.1-rh6-64.tgz
Run the install script: # ./install.sh
The archives are:
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
Note that the original patches included in this advisory have been deprecated in favor of a newer set of patches listed above that fixes additional issues covered in TNS-2014-04.
Which can be downloaded from:
SecurityCenter Download Page (https://support.tenable.com/support-center/index.php?x=&mod_id=160)
To patch the Tenable Appliance please download the file from:
Tenable Appliance Download Page (https://support.tenable.com/support-center/index.php?x=&mod_id=230)
File md5sum SC4-ApacheUpgrade.tar.gz [3dd17e456d34326050d501dac02d4eda]
To apply the patch update, navigate to the Administration tab. Then from the Update Appliance section, click on Choose file, browse to the location where the update file archive was saved, and click on "Apply Update".
Note that the original patch included in this advisory (SC-OpenSSL-patch.tar.gz [c33e5d2bafb5679103384688200dddd3]) has been deprecated in favor of a newer patch that fixes additional issues covered in TNS-2014-04.
If you also deploy Nessus, PVS, or LCE, note that those programs are not affected by this issue. Both Nessus and PVS have plugins that will detect this vulnerability.
Additional References
http://heartbleed.comhttp://www.openssl.org/news/secadv_20140407.txt
http://filippo.io/Heartbleed/
https://github.com/FiloSottile/Heartbleed
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]
Contact our sales team