jroseace 0 Posted September 21, 2021 Share Posted September 21, 2021 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. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 375 Posted September 22, 2021 ESET Staff Share Posted September 22, 2021 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. Link to comment Share on other sites More sharing options...
jroseace 0 Posted September 22, 2021 Author Share Posted September 22, 2021 OK, thanks Martin. I think we'll just have to make a business case exemption for this one, and wait for an update. Link to comment Share on other sites More sharing options...
ESET Moderators Solution Peter Randziak 948 Posted September 23, 2021 ESET Moderators Solution Share Posted September 23, 2021 Hello @jroseace, new build of Apache HTTP Proxy with this issue covered will be released. Peter P_EP-25295 Link to comment Share on other sites More sharing options...
Recommended Posts