https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 06:31:04 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-01024 bdu:2024-01024 https://cve.radiocsirt.org/vuln/bdu:2024-01024 https://cve.radiocsirt.org/vuln/bit-modsecurity-2024-1019 <p><strong>Affected:</strong> Bitnami: modsecurity</p> <p>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.</p> <p><strong>Affected:</strong> Bitnami: modsecurity</p> <p>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.</p> https://cve.radiocsirt.org/vuln/bit-modsecurity-2024-1019 https://cve.radiocsirt.org/vuln/euvd-2026-244975 EUVD-2026-244975 https://cve.radiocsirt.org/vuln/euvd-2026-244975 https://cve.radiocsirt.org/vuln/fkie_cve-2024-1019 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-1019 https://cve.radiocsirt.org/vuln/ghsa-w56r-g989-xqw3 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ghsa-w56r-g989-xqw3 https://cve.radiocsirt.org/vuln/gsd-2024-1019 gsd-2024-1019 https://cve.radiocsirt.org/vuln/gsd-2024-1019 https://cve.radiocsirt.org/vuln/opensuse-su-2024:13732-1 <p>libmodsecurity3-3.0.12-1.1 on GA media</p> <p>libmodsecurity3-3.0.12-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:13732-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-1019 <p><strong>Affected:</strong> Ubuntu:20.04:LTS: modsecurity, Ubuntu:22.04:LTS: modsecurity, Ubuntu:24.04:LTS: modsecurity, Ubuntu:25.10: modsecurity, Ubuntu:26.04:LTS: modsecurity</p> <p>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.</p> <p><strong>Affected:</strong> Ubuntu:20.04:LTS: modsecurity, Ubuntu:22.04:LTS: modsecurity, Ubuntu:24.04:LTS: modsecurity, Ubuntu:25.10: modsecurity, Ubuntu:26.04:LTS: modsecurity</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-1019 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0258 <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Trustwave ModSecurity ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Trustwave ModSecurity ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0258