OR
     *cpe:2.3:a:trustwave:modsecurity:*:*:*:*:*:*:*:* versions from (including) 3.0.0 from (including) 3.0.4

OR
     *cpe:2.3:a:owasp:modsecurity:*:*:*:*:*:*:*:* versions from (including) 3.0.0 from (including) 3.0.4

http://packetstormsecurity.com/files/159185/ModSecurity-3.0.x-Denial-Of-Service.html

http://seclists.org/fulldisclosure/2020/Sep/32

https://coreruleset.org/20200914/cve-2020-15598/

https://www.debian.org/security/2020/dsa-4765

https://www.modsecurity.org

MITRE disputed

** DISPUTED ** Trustwave ModSecurity 3.x through 3.0.4 allows denial of service via a special request. NOTE: The discoverer reports "Trustwave has signaled they are disputing our claims." The CVE suggests that there is a security issue with how ModSecurity handles regular expressions that can result in a Denial of Service condition. The vendor does not consider this as a security issue because1) there is no default configuration issue here. An attacker would need to know that a rule using a potentially problematic regular expression was in place, 2) the attacker would need to know the basic nature of the regular expression itself to exploit any resource issues. It's well known that regular expression usage can be taxing on system resources regardless of the use case. It is up to the administrator to decide on when it is appropriate to trade resources for potential security benefit.

Trustwave ModSecurity 3.x through 3.0.4 allows denial of service via a special request. NOTE: The discoverer reports "Trustwave has signaled they are disputing our claims." The CVE suggests that there is a security issue with how ModSecurity handles regular expressions that can result in a Denial of Service condition. The vendor does not consider this as a security issue because1) there is no default configuration issue here. An attacker would need to know that a rule using a potentially problematic regular expression was in place, 2) the attacker would need to know the basic nature of the regular expression itself to exploit any resource issues. It's well known that regular expression usage can be taxing on system resources regardless of the use case. It is up to the administrator to decide on when it is appropriate to trade resources for potential security benefit

NIST AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

NIST (AV:N/AC:L/Au:N/C:N/I:N/A:P)

NIST CWE-835

OR
     *cpe:2.3:a:trustwave:modsecurity:*:*:*:*:*:*:*:* versions from (including) 3.0.0 up to (including) 3.0.4

OR
     *cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

http://packetstormsecurity.com/files/159185/ModSecurity-3.0.x-Denial-Of-Service.html No Types Assigned

http://packetstormsecurity.com/files/159185/ModSecurity-3.0.x-Denial-Of-Service.html Third Party Advisory, VDB Entry

http://seclists.org/fulldisclosure/2020/Sep/32 No Types Assigned

http://seclists.org/fulldisclosure/2020/Sep/32 Mailing List, Third Party Advisory

https://coreruleset.org/20200914/cve-2020-15598/ No Types Assigned

https://coreruleset.org/20200914/cve-2020-15598/ Exploit, Patch, Third Party Advisory

https://www.debian.org/security/2020/dsa-4765 No Types Assigned

https://www.debian.org/security/2020/dsa-4765 Third Party Advisory

https://www.modsecurity.org No Types Assigned

https://www.modsecurity.org Product, Vendor Advisory