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

[R12] OpenSSL '20160301' Advisory Affects Tenable Products

Critical

Synopsis

Nessus is potentially impacted by several vulnerabilities in OpenSSL that were recently disclosed and fixed. Note that due to the time involved in doing a full analysis of each issue, Tenable has opted to upgrade the included version of OpenSSL as a precaution, and to save time. The issues include:

  • CVE-2016-0800 Secure Sockets Layer Version 2 (SSLv2) Cross-Protocol TLS Session Decryption (DROWN)
  • CVE-2016-0705 OpenSSL DSA Private Key Handling Double-free Memory Corruption
  • CVE-2016-0702 OpenSSL Cache-bank Conflict Handling Side-channel RSA Key Disclosure
  • CVE-2016-0797 OpenSSL crypto/bn/bn_print.c BN_hex2bn() / BN_dec2bn() Functions NULL Pointer Dereference Heap Corruption
  • CVE-2016-0799 OpenSSL crypto/bio/b_print.c doapr_outch() Function Memory Allocation Failure Memory Corruption
  • CVE-2016-0799 OpenSSL crypto/bio/b_print.c fmtstr() Function Out-of-bounds Read Issue
  • CVE-2016-0798 OpenSSL SRP Server apps/s_server.c SRP_VBASE_get_by_user Method Username Handling Memory Exhaustion Remote DoS
  • CVE-2016-0703 OpenSSL s2_srvr.c Non-zero Clear Key Length Handling SSLv2 Master Key Disclosure
  • CVE-2016-0704 OpenSSL Simple s2_srvr.c RSA CMS Signature Bleichenbacher Weakness

Notes and caveats:

  • CVE-2016-0703 and CVE-2016-0704 were actually fixed in 1.0.2a, but mentioned in the OpenSSL advisory for 1.0.2g.
  • At present, SecurityCenter and LCE do not enable SSLv2 and are not impacted by the 'DROWN' vulnerability, or any other based on SSLv2 flaws.
  • The Tenable Appliance does not enable SSLv2, and based on internal evaluation, does not appear to be impacted by the remaining issues.
  • LCE was not evaluated for the non-SSLv2 issues, as upgrading to the newer OpenSSL was faster.
  • Nessus Agents are not affected by these issues, as they do not act as an SSL server.
  • Other Tenable products (including PVS 5.0.0), are still being evaluated.
  • Please note that Tenable strongly recommends that Tenable products be installed on a subnet that is not Internet addressable.

Solution

Nessus:

Tenable has released version 6.5.6 that corresponds to the supported operating systems and architectures. This version bundles the updated OpenSSL library (1.0.1s), which is not affected. Version 6.6.0 of Nessus bundles OpenSSL 1.0.2g.

To update your Nessus installation, follow these steps:

SecurityCenter:

Tenable has released version 5.3.0 of SecurityCenter that addresses these vulnerabilities by including OpenSSL 1.0.1s. Upgrade information can be obtained from:

http://static.tenable.com/prod_docs/upgrade_security_center.html

LCE:

Tenable has released version 4.8.0, which bundles OpenSSL 1.0.2g, to address any potential issues. It is available at:

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

PVS:

Tenable has released PVS version 4.4.1 that corresponds to the supported operating systems and architectures. This version bundles the updated OpenSSL library (1.0.2g), which is not affected. It is available at:

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

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]