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

[R6] SecurityCenter 5.4.1 Fixes Multiple Vulnerabilities

Critical

Synopsis

SecurityCenter has recently been discovered to have several vulnerabilities. Two were reported by external parties while the rest were discovered during internal testing. Note that the library vulnerabilities were not fully diagnosed so SecurityCenter may or may not be impacted. Tenable opted to upgrade the libraries as it was more efficient. Details of the issues (with internal IDs for your tracking pleasure):

  • 5 stored XSS that require authentication (31263, 31309, 31283, 31310, 31311) discovered internally by Chris Broome
  • 1 stored XSS that requires authentication (12277) discovered internally by Kyle Teahan
  • 1 stored XSS that requires authentication (31374) discovered internally
  • 2 stored XSS that require authentication (31518, 31410) discovered and reported to Tenable by Kaustubh Padwad
  • jQuery UI was upgraded to 1.12.0 potentially fixing 1 vulnerability
  • PHP was upgraded to 5.6.28 fixing 4 vulnerabilities, 14 vulnerabilities from 5.6.27, 13 vulnerabilities from 5.6.26, and 19 from 5.6.25 (some of which are covered by IAVM 2016-B-0133)
  • OpenSSL was upgraded to 1.0.2j fixing 1 vulnerability

Tenable would like to thank Kaustubh Padwad for privately reporting issues and giving us time to provide a fix for customers.

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

Solution

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

Risk Information

Tenable Advisory ID: TNS-2016-19
Risk Factor: Critical
Credit:
Kaustubh Padwad [<a href="http://twitter.com/s3curityb3ast" target="_blank">@s3curityb3ast</a>]
Chris Broome [<a href="http://www.tenable.com/" target="_blank">Tenable Network Security</a>]
Kyle Teahan [<a href="http://www.tenable.com/" target="_blank">Tenable Network Security</a>]
CVSSv2 Base / Temporal Score
Stored XSS: 4.0 / 3.1
PHP Issues: 10.0 / 7.4
CVSSv2 Vector:
Stored XSS: (AV:N/AC:L/Au:S/C:N/I:P/A:N/E:POC/RL:OF/RC:C)
PHP Issues: (AV:N/AC:L/Au:N/C:C/I:C/A:C/E:U/RL:OF/RC:C)
Additional Keywords:
IAVM 2016-B-0133

Affected Products

SecurityCenter 5.4.0

Disclosure Timeline

2016-10-01 - Stored XSS (31410) reported to Tenable by Kaustubh Padwad
2016-10-03 - Tenable confirms receipt, opens ticket with Dev
2016-11-03 - Stored XSS (31518) reported to Tenable by Kaustubh Padwad
2016-11-03 - Tenable confirms receipt, opens ticket with Dev

Advisory Timeline

2016-11-28 - [R1] Initial Release
2016-11-28 - [R2] Added VDB IDs, OpenSSL reference
2016-11-28 - [R3] Touch-ups to internal IDs for XSS
2016-11-29 - [R4] Added IDs for the new XSS
2016-12-07 - [R5] Corrected the upgraded PHP version, added additional vuln counts for PHP versions
2017-02-28 - [R6] Adjust CVSS for worst-case scenario (AV:A -> AV:N)