Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

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

LEM vulnerability to OpenSSL

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

Views: 961 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