Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Log & Event Manager (LEM) > LEM vulnerability to OpenSSL

LEM vulnerability to OpenSSL

Created by Craig O’ Neill, last modified by MindTouch on Jun 23, 2016

Views: 87 Votes: 1 Revisions: 5


This article provides brief information on LEM vulnerability to OpenSSL issues.


LEM version 6.2


The security team have simply identified that Openssl exists on the LEM appliance.

The Embedded Tomcat i.e. web console - Does use SSL/TLS for port 8443. We don't specify whether to use APR (OpenSSL) or JSSE connector so Tomcat decides for us.

It prefers APR but since it is not installed on our Debian appliance (libapr), the native connector is used i.e. JSSE.

So, whereis OpenSSL installed?

Our PostgreSQL database uses OpenSSL for secured connections.
This database is used solely for users who use SolarWinds NTA to send Cisco Netflow to LEM.

Unless you use LEM for Netflow, OpenSSL is not an issue and LEM is not open to any of the related OpenSSL vulnerabilities..


Even so this should not be accessible from outside your network.


Disable flow service


Login as cmc > service > disableflow.


This will stop the service that utilises OpenSSL.

It may not remove it from the scope of the scanner but it will enforce a Cul de Sac.




Last modified