Bug 2131315 (CVE-2022-39955) - CVE-2022-39955 mod_security_crs: Multiple charsets defined in Content-Type header
Summary: CVE-2022-39955 mod_security_crs: Multiple charsets defined in Content-Type he...
Keywords:
Status: NEW
Alias: CVE-2022-39955
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2131316 2131341 2131342
Blocks: 2128790
TreeView+ depends on / blocked
 
Reported: 2022-09-30 16:52 UTC by Guilherme de Almeida Suckevicz
Modified: 2022-10-07 13:56 UTC (History)
2 users (show)

Fixed In Version: mod_security_crs 3.2.2, mod_security_crs 3.3.3
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in the OWASP ModSecurity Core Rule Set. A specially crafted HTTP Content-Type header field allows an encoded payload bypass detection, which may be decoded in the back-end application.
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2022-09-30 16:52:51 UTC
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.

Reference:
https://coreruleset.org/20220919/crs-version-3-3-3-and-3-2-2-covering-several-cves/

Comment 1 Guilherme de Almeida Suckevicz 2022-09-30 16:53:05 UTC
Created mod_security_crs tracking bugs for this issue:

Affects: fedora-all [bug 2131316]


Note You need to log in before you can comment on or make changes to this bug.