First published: Tue Jan 30 2024(Updated: )
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.
Credit: vulnerability@ncsc.ch
Affected Software | Affected Version | How to fix |
---|---|---|
Trustwave ModSecurity | >=3.0.0<3.0.12 |
Upgrade to ModSecurity 3.0.12.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-1019 is considered a medium severity vulnerability due to its potential for WAF bypass.
To fix CVE-2024-1019, upgrade ModSecurity to a version higher than 3.0.11.
CVE-2024-1019 affects ModSecurity versions from 3.0.0 to 3.0.11.
CVE-2024-1019 allows attackers to bypass security controls by crafting specific request URLs.
The maintainers of ModSecurity are responsible for addressing CVE-2024-1019 by providing patches and updates.