Vulnerabilities · 2024 · Owasp
CVE-2024-1019
Owasp Modsecurity vulnerability
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.
Affected products
Modsecurity. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Owasp Modsecurity runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
More vulnerabilities in Owasp products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.