Protection Mechanism Failure Affecting mod_security_crs package, versions *


Severity

Recommended
medium

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.12% (32nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-MODSECURITYCRS-3038094
  • published1 Oct 2022
  • disclosed19 Sept 2022

Introduced: 19 Sep 2022

CVE-2022-39957  (opens in a new tab)
CWE-693  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:8 mod_security_crs.

NVD Description

Note: Versions mentioned in the description apply only to the upstream mod_security_crs package and not the mod_security_crs package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1