Nessus reports critical OpenSSL vulnerability on ESET Protect server

[jroseace 0]

We have an ESET Protect on-prem server we just set up in the last few weeks. Auto-update is on - nothing to download.

Nessus reports a critical vulnerability in OpenSSL 1.1.1 - see image.

Is there any remediation for this?

Thanks.

[MartinK 384]

In case standard Apache HTTP proxy distributed with ESET PROTECT is used, TLS communication is used only when ESET Dynamic Threat Defense functionality is used in your environment, and even in this case it is used only for outgoing connections.
But regardless of that, it might be possible to disable respective Apache modules or just remove problematic library, and caching should probably work - but I have not verified that nor it is tested scenario - but it should not be crucial for standard caching functionality. I would recommend it only in a way fast solution is required, even in case that vulnerabilities are most probably not affecting your environment.
 

[jroseace 0]

OK, thanks Martin. I think we'll just have to make a business case exemption for this one, and wait for an update.

[Peter Randziak 1,181]

Hello @jroseace,

new build of Apache HTTP Proxy with this issue covered will be released.

Peter

P_EP-25295