The OWASP ModSecurity Core Rule Set (CRS) is affected by a response body bypass. A client can issue an HTTP Accept header field containing an optional "charset" parameter in order to receive the response in an encoded form. Depending on the "charset", this response can not be decoded by the web application firewall. A restricted resource, access to which would ordinarily be detected, may therefore bypass detection. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are advised to upgrade to 3.2.2 and 3.3.3 respectively.

The remote Redhat Enterprise Linux 8 host has one or more packages installed that are affected by multiple vulnerabilities that have been acknowledged by the vendor but will not be patched.

  - mod_security_crs: Content-Type or Content-Transfer-Encoding MIME header fields abuse (CVE-2022-39956)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a partial rule set bypass by submitting a     specially crafted HTTP Content-Type header field that indicates multiple character encoding schemes. A     vulnerable back-end can potentially be exploited by declaring multiple Content-Type charset names and     therefore bypassing the configurable CRS Content-Type header charset allow list. An encoded payload can     bypass CRS detection this way and may then be decoded by the backend. The legacy CRS versions 3.0.x and     3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are     advised to upgrade to 3.2.2 and 3.3.3 respectively. (CVE-2022-39955)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a response body bypass. A client can issue an     HTTP Accept header field containing an optional charset parameter in order to receive the response in an     encoded form. Depending on the charset, this response can not be decoded by the web application     firewall. A restricted resource, access to which would ordinarily be detected, may therefore bypass     detection. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported     versions 3.2.1 and 3.3.2. Integrators and users are advised to upgrade to 3.2.2 and 3.3.3 respectively.
    (CVE-2022-39957)

Note that Nessus has not tested for these issues but has instead relied on the package manager's report that the package is installed.

The remote Redhat Enterprise Linux 9 host has one or more packages installed that are affected by multiple vulnerabilities that have been acknowledged by the vendor but will not be patched.

  - mod_security_crs: Content-Type or Content-Transfer-Encoding MIME header fields abuse (CVE-2022-39956)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a partial rule set bypass by submitting a     specially crafted HTTP Content-Type header field that indicates multiple character encoding schemes. A     vulnerable back-end can potentially be exploited by declaring multiple Content-Type charset names and     therefore bypassing the configurable CRS Content-Type header charset allow list. An encoded payload can     bypass CRS detection this way and may then be decoded by the backend. The legacy CRS versions 3.0.x and     3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are     advised to upgrade to 3.2.2 and 3.3.3 respectively. (CVE-2022-39955)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a response body bypass. A client can issue an     HTTP Accept header field containing an optional charset parameter in order to receive the response in an     encoded form. Depending on the charset, this response can not be decoded by the web application     firewall. A restricted resource, access to which would ordinarily be detected, may therefore bypass     detection. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported     versions 3.2.1 and 3.3.2. Integrators and users are advised to upgrade to 3.2.2 and 3.3.3 respectively.
    (CVE-2022-39957)

Note that Nessus has not tested for these issues but has instead relied on the package manager's report that the package is installed.

The remote host is affected by the vulnerability described in GLSA-202305-25 (OWASP ModSecurity Core Rule Set: Multiple Vulnerabilities)

  - OWASP ModSecurity Core Rule Set 3.1.x before 3.1.2, 3.2.x before 3.2.1, and 3.3.x before 3.3.2 is affected     by a Request Body Bypass via a trailing pathname. (CVE-2021-35368)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a partial rule set bypass by submitting a     specially crafted HTTP Content-Type header field that indicates multiple character encoding schemes. A     vulnerable back-end can potentially be exploited by declaring multiple Content-Type charset names and     therefore bypassing the configurable CRS Content-Type header charset allow list. An encoded payload can     bypass CRS detection this way and may then be decoded by the backend. The legacy CRS versions 3.0.x and     3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are     advised to upgrade to 3.2.2 and 3.3.3 respectively. (CVE-2022-39955)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a partial rule set bypass for HTTP multipart     requests by submitting a payload that uses a character encoding scheme via the Content-Type or the     deprecated Content-Transfer-Encoding multipart MIME header fields that will not be decoded and inspected     by the web application firewall engine and the rule set. The multipart payload will therefore bypass     detection. A vulnerable backend that supports these encoding schemes can potentially be exploited. The     legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and     3.3.2. Integrators and users are advised upgrade to 3.2.2 and 3.3.3 respectively. The mitigation against     these vulnerabilities depends on the installation of the latest ModSecurity version (v2.9.6 / v3.0.8).
    (CVE-2022-39956)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a response body bypass. A client can issue an     HTTP Accept header field containing an optional charset parameter in order to receive the response in an     encoded form. Depending on the charset, this response can not be decoded by the web application     firewall. A restricted resource, access to which would ordinarily be detected, may therefore bypass     detection. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported     versions 3.2.1 and 3.3.2. Integrators and users are advised to upgrade to 3.2.2 and 3.3.3 respectively.
    (CVE-2022-39957)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a response body bypass to sequentially exfiltrate     small and undetectable sections of data by repeatedly submitting an HTTP Range header field with a small     byte range. A restricted resource, access to which would ordinarily be detected, may be exfiltrated from     the backend, despite being protected by a web application firewall that uses CRS. Short subsections of a     restricted resource may bypass pattern matching techniques and allow undetected access. The legacy CRS     versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2.
    Integrators and users are advised to upgrade to 3.2.2 and 3.3.3 respectively and to configure a CRS     paranoia level of 3 or higher. (CVE-2022-39958)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Debian 10 host has a package installed that is affected by multiple vulnerabilities as referenced in the dla-3293 advisory.

  - A SQL injection bypass (aka PL1 bypass) exists in OWASP ModSecurity Core Rule Set (owasp-modsecurity-crs)     through v3.1.0-rc3 via {`a`b} where a is a special function name (such as if) and b is the SQL statement     to be executed. (CVE-2018-16384)

  - Modsecurity owasp-modsecurity-crs 3.2.0 (Paranoia level at PL1) has a SQL injection bypass vulnerability.
    Attackers can use the comment characters and variable assignments in the SQL syntax to bypass Modsecurity     WAF protection and implement SQL injection attacks on Web applications. (CVE-2020-22669)

  - OWASP ModSecurity Core Rule Set 3.1.x before 3.1.2, 3.2.x before 3.2.1, and 3.3.x before 3.3.2 is affected     by a Request Body Bypass via a trailing pathname. (CVE-2021-35368)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a partial rule set bypass by submitting a     specially crafted HTTP Content-Type header field that indicates multiple character encoding schemes. A     vulnerable back-end can potentially be exploited by declaring multiple Content-Type charset names and     therefore bypassing the configurable CRS Content-Type header charset allow list. An encoded payload can     bypass CRS detection this way and may then be decoded by the backend. The legacy CRS versions 3.0.x and     3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are     advised to upgrade to 3.2.2 and 3.3.3 respectively. (CVE-2022-39955)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a partial rule set bypass for HTTP multipart     requests by submitting a payload that uses a character encoding scheme via the Content-Type or the     deprecated Content-Transfer-Encoding multipart MIME header fields that will not be decoded and inspected     by the web application firewall engine and the rule set. The multipart payload will therefore bypass     detection. A vulnerable backend that supports these encoding schemes can potentially be exploited. The     legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and     3.3.2. Integrators and users are advised upgrade to 3.2.2 and 3.3.3 respectively. The mitigation against     these vulnerabilities depends on the installation of the latest ModSecurity version (v2.9.6 / v3.0.8).
    (CVE-2022-39956)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a response body bypass. A client can issue an     HTTP Accept header field containing an optional charset parameter in order to receive the response in an     encoded form. Depending on the charset, this response can not be decoded by the web application     firewall. A restricted resource, access to which would ordinarily be detected, may therefore bypass     detection. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported     versions 3.2.1 and 3.3.2. Integrators and users are advised to upgrade to 3.2.2 and 3.3.3 respectively.
    (CVE-2022-39957)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a response body bypass to sequentially exfiltrate     small and undetectable sections of data by repeatedly submitting an HTTP Range header field with a small     byte range. A restricted resource, access to which would ordinarily be detected, may be exfiltrated from     the backend, despite being protected by a web application firewall that uses CRS. Short subsections of a     restricted resource may bypass pattern matching techniques and allow undetected access. The legacy CRS     versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2.
    Integrators and users are advised to upgrade to 3.2.2 and 3.3.3 respectively and to configure a CRS     paranoia level of 3 or higher. (CVE-2022-39958)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 35 host has packages installed that are affected by multiple vulnerabilities as referenced in the FEDORA-2022-85a85c84b3 advisory.

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a partial rule set bypass by submitting a     specially crafted HTTP Content-Type header field that indicates multiple character encoding schemes. A     vulnerable back-end can potentially be exploited by declaring multiple Content-Type charset names and     therefore bypassing the configurable CRS Content-Type header charset allow list. An encoded payload can     bypass CRS detection this way and may then be decoded by the backend. The legacy CRS versions 3.0.x and     3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are     advised to upgrade to 3.2.2 and 3.3.3 respectively. (CVE-2022-39955)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a partial rule set bypass for HTTP multipart     requests by submitting a payload that uses a character encoding scheme via the Content-Type or the     deprecated Content-Transfer-Encoding multipart MIME header fields that will not be decoded and inspected     by the web application firewall engine and the rule set. The multipart payload will therefore bypass     detection. A vulnerable backend that supports these encoding schemes can potentially be exploited. The     legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and     3.3.2. Integrators and users are advised upgrade to 3.2.2 and 3.3.3 respectively. The mitigation against     these vulnerabilities depends on the installation of the latest ModSecurity version (v2.9.6 / v3.0.8).
    (CVE-2022-39956)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a response body bypass. A client can issue an     HTTP Accept header field containing an optional charset parameter in order to receive the response in an     encoded form. Depending on the charset, this response can not be decoded by the web application     firewall. A restricted resource, access to which would ordinarily be detected, may therefore bypass     detection. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported     versions 3.2.1 and 3.3.2. Integrators and users are advised to upgrade to 3.2.2 and 3.3.3 respectively.
    (CVE-2022-39957)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a response body bypass to sequentially exfiltrate     small and undetectable sections of data by repeatedly submitting an HTTP Range header field with a small     byte range. A restricted resource, access to which would ordinarily be detected, may be exfiltrated from     the backend, despite being protected by a web application firewall that uses CRS. Short subsections of a     restricted resource may bypass pattern matching techniques and allow undetected access. The legacy CRS     versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2.
    Integrators and users are advised to upgrade to 3.2.2 and 3.3.3 respectively and to configure a CRS     paranoia level of 3 or higher. (CVE-2022-39958)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 36 host has packages installed that are affected by multiple vulnerabilities as referenced in the FEDORA-2022-90708b46e3 advisory.

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a partial rule set bypass by submitting a     specially crafted HTTP Content-Type header field that indicates multiple character encoding schemes. A     vulnerable back-end can potentially be exploited by declaring multiple Content-Type charset names and     therefore bypassing the configurable CRS Content-Type header charset allow list. An encoded payload can     bypass CRS detection this way and may then be decoded by the backend. The legacy CRS versions 3.0.x and     3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are     advised to upgrade to 3.2.2 and 3.3.3 respectively. (CVE-2022-39955)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a partial rule set bypass for HTTP multipart     requests by submitting a payload that uses a character encoding scheme via the Content-Type or the     deprecated Content-Transfer-Encoding multipart MIME header fields that will not be decoded and inspected     by the web application firewall engine and the rule set. The multipart payload will therefore bypass     detection. A vulnerable backend that supports these encoding schemes can potentially be exploited. The     legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and     3.3.2. Integrators and users are advised upgrade to 3.2.2 and 3.3.3 respectively. The mitigation against     these vulnerabilities depends on the installation of the latest ModSecurity version (v2.9.6 / v3.0.8).
    (CVE-2022-39956)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a response body bypass. A client can issue an     HTTP Accept header field containing an optional charset parameter in order to receive the response in an     encoded form. Depending on the charset, this response can not be decoded by the web application     firewall. A restricted resource, access to which would ordinarily be detected, may therefore bypass     detection. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported     versions 3.2.1 and 3.3.2. Integrators and users are advised to upgrade to 3.2.2 and 3.3.3 respectively.
    (CVE-2022-39957)

  - The OWASP ModSecurity Core Rule Set (CRS) is affected by a response body bypass to sequentially exfiltrate     small and undetectable sections of data by repeatedly submitting an HTTP Range header field with a small     byte range. A restricted resource, access to which would ordinarily be detected, may be exfiltrated from     the backend, despite being protected by a web application firewall that uses CRS. Short subsections of a     restricted resource may bypass pattern matching techniques and allow undetected access. The legacy CRS     versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2.
    Integrators and users are advised to upgrade to 3.2.2 and 3.3.3 respectively and to configure a CRS     paranoia level of 3 or higher. (CVE-2022-39958)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
198990	RHEL 8 : mod_security_crs (Unpatched Vulnerability)	Nessus	Red Hat Local Security Checks	critical
198873	RHEL 9 : mod_security_crs (Unpatched Vulnerability)	Nessus	Red Hat Local Security Checks	critical
176193	GLSA-202305-25 : OWASP ModSecurity Core Rule Set: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	critical
170888	Debian DLA-3293-1 : modsecurity-crs - LTS security update	Nessus	Debian Local Security Checks	critical
169232	Fedora 35 : mod_security / mod_security_crs (2022-85a85c84b3)	Nessus	Fedora Local Security Checks	critical
169143	Fedora 36 : mod_security / mod_security_crs (2022-90708b46e3)	Nessus	Fedora Local Security Checks	critical

Detections

Analytics

CVE-2022-39957

high

Tenable Plugins

critical

critical

critical

critical

critical

critical