Incorrect Authorization Affecting mod_security_crs package, versions *


Severity

Recommended
medium

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.29% (52nd 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 Learn

Learn about Incorrect Authorization vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL8-MODSECURITYCRS-3038098
  • published1 Oct 2022
  • disclosed19 Sept 2022

Introduced: 19 Sep 2022

CVE-2022-39958  (opens in a new tab)
CWE-863  (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 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.

CVSS Base Scores

version 3.1