This report is a daily analysis of all published vulnerabilities in any product, weaknesses in technologies, exploits Internet wide, current internet threats associated with platforms and products our customer use, and if any action is required to protect their assets from these these vulnerabilities, weaknesses and exploits depending on the Atomicorp product they are using.
Please see this forum post for an explanation of the categories used in this report.
Note: CVEs are sometimes created after a vulnerability is published (sometimes far after it has been made public). When CVEs are referenced, it is because a CVE was created today, not because an issue was resolved today, and it is included here for reference.
ASL users
Summary: No action required for non-Litespeed users. For Litespeed user, ensure that you have placed the ASL WAF in front of Litespeed and you will be protected from the Litespeed vulnerability below.
Already protect against/Known Method/No update required
OpenVAS Greenbone Security Assistant Cross Site Scripting (When protected by the ASL WAF)
LiteSpeed Web Server 5.1.0 HTTP Header Injection (When protected by the ASL WAF)
OpenCart LFI
Not already protected against/New Method/Update Available
None.
Not already protected against/Doesnt protect against/Solution
None.
Potential Vulnerability/Solution
None.
Rules only users
Summary: For Litespeed users, ensure that you have placed a third party webserver (e.g. Apache) running modsecurity and the rules in front of Litespeed and you will be protected from the Litespeed vulnerability below.
Already protect against/Known Method/No update required
OpenCart LFI
Already protect against/Known Method/No update required
None.
Not already protected against/Doesnt protect against/Solution
None.
Potential Vulnerability/Solution
OpenVAS Greenbone Security Assistant Cross Site Scripting (If modsecurity is protecting the service via proxy, then this vulnerability is addressed)
LiteSpeed Web Server 5.1.0 HTTP Header Injection (If modsecurity via a third party web server is protecting the service via proxy, then this vulnerability is addressed, if using the internal WAF function in Litespeed this may not be addressed)