ModSecurity / libModSecurity 3.0.0 to 3.0.11 is affected by a WAF bypass for path-based payloads submitted via specially crafted request URLs. ModSecurity v3 decodes percent-encoded characters present in request URLs before it separates the URL path component from the optional query string component. This results in an impedance mismatch versus RFC compliant back-end applications. The vulnerability hides an attack payload in the path component of the URL from WAF rules inspecting it. A back-end may be vulnerable if it uses the path component of request URLs to construct queries. Integrators and users are advised to upgrade to 3.0.12. The ModSecurity v2 release line is not affected by this vulnerability.
References
Configurations
History
20 Feb 2024, 02:15
Type | Values Removed | Values Added |
---|---|---|
References |
|
08 Feb 2024, 16:35
Type | Values Removed | Values Added |
---|---|---|
CWE | NVD-CWE-noinfo | |
First Time |
Trustwave modsecurity
Trustwave |
|
CPE | cpe:2.3:a:trustwave:modsecurity:*:*:*:*:*:*:*:* | |
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 8.6 |
References | () https://owasp.org/www-project-modsecurity/tab_cves#cve-2024-1019-2024-01-30 - Patch, Vendor Advisory |
30 Jan 2024, 16:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2024-01-30 16:15
Updated : 2024-02-28 20:54
NVD link : CVE-2024-1019
Mitre link : CVE-2024-1019
CVE.ORG link : CVE-2024-1019
JSON object : View
Products Affected
trustwave
- modsecurity
CWE