Hello everyone,
We are still running OpenLiteSpeed on some CentOS 7 servers and are looking for advice regarding the recent LSQUIC security vulnerability.
Since CentOS 7 is no longer actively maintained, we are concerned about whether the latest security fixes can still be applied safely on this platform.
In the meantime, we would like to understand the available mitigation options.
Has anyone running OpenLiteSpeed on CentOS 7 already addressed this vulnerability by disabling HTTP/3 (QUIC)?
In particular:
For those who have disabled HTTP/3/QUIC on CentOS 7, which exact command or configuration change did you use? Did you modify the OpenLiteSpeed configuration directly, use the WebAdmin interface, or use another method?
We would particularly appreciate feedback from anyone who has already implemented this mitigation in a production environment.
We are planning our OS migration, but would like to secure our existing servers in the meantime without introducing unnecessary changes or downtime.
Thank you for your help and suggestions.
We are still running OpenLiteSpeed on some CentOS 7 servers and are looking for advice regarding the recent LSQUIC security vulnerability.
Since CentOS 7 is no longer actively maintained, we are concerned about whether the latest security fixes can still be applied safely on this platform.
In the meantime, we would like to understand the available mitigation options.
Has anyone running OpenLiteSpeed on CentOS 7 already addressed this vulnerability by disabling HTTP/3 (QUIC)?
In particular:
- Is disabling HTTP/3/QUIC considered a sufficient mitigation for this vulnerability?
- Does disabling QUIC completely prevent exploitation of the LSQUIC vulnerability, or are there other components that also need to be addressed?
- Is there a patched OpenLiteSpeed build that is compatible with CentOS 7?
For those who have disabled HTTP/3/QUIC on CentOS 7, which exact command or configuration change did you use? Did you modify the OpenLiteSpeed configuration directly, use the WebAdmin interface, or use another method?
We would particularly appreciate feedback from anyone who has already implemented this mitigation in a production environment.
We are planning our OS migration, but would like to secure our existing servers in the meantime without introducing unnecessary changes or downtime.
Thank you for your help and suggestions.
