splunk is currently locking the dll libeay32.dll from the wrong directory. this is causing our main security product on the endpoints to lock and fail. This needs to be remediated in order to secure our environment.
i believe the issue is directly related to how splunk searchs for libeay32.dll. I believe the application is using a */libeay32.dll method of searching for the path for libeay32.dll and since our security product is alphabetically first, it is selecting libeay32.dll from the bit9 path and locking it up in memory causing the applications to fail.
bit9 path: c:program files (x86)Bit9Parity Agentlibeay32.dll
splunk path: c:program filessplunkunkiversalforwarderbinlibeay32.dll