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

[R3] Log Correlation Engine (LCE) 4.8.0 Fixes Third-party Library

Medium

Synopsis

The Log Correlation Engine (LCE) uses the third-party Libxml2 library for some XML parsing routines. A vulnerability was found and patched in Libxml2 recently. Tenable has not evaluated this vulnerability beyond acknowledging that user-supplied XML input can be parsed by LCE. As such, the developer team upgraded the library as a precaution without further testing (that is "possibly affected" for mature vulnerability databases!). <doge>Very speed, less risk</doge>!

CVE-2015-8035 - Libxml2 contains an infinite loop condition in the xz_decomp() function in xzlib.c that is triggered when handling xz compressed XML content. This may allow a context-dependent attacker to exhaust available system resources.

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

Solution

Log Correlation Engine (LCE)

Tenable has released the Log Correlation Engine (LCE) 4.8.0 that address this potential issue. The updated version can be found at:

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

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]