PT-2022-25142 · Owasp+1 · Owasp Modsecurity Core Rule Set+1
Jan Gora
+1
·
Published
2022-09-20
·
Updated
2025-08-09
·
CVE-2022-39955
CVSS v3.1
9.8
Critical
| Vector | AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Name of the Vulnerable Software and Affected Versions
OWASP ModSecurity Core Rule Set (CRS) versions 3.0.x through 3.3.2
Description
The issue concerns 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, thereby bypassing the configurable CRS Content-Type header charset allow list. An encoded payload can bypass CRS detection and may then be decoded by the backend.Recommendations
For versions 3.0.x and 3.1.x, upgrade to a newer version as these are legacy and no longer supported.
For version 3.2.1, upgrade to 3.2.2.
For version 3.3.2, upgrade to 3.3.3.
As a temporary workaround, consider restricting the use of multiple
charset names in the Content-Type header field to minimize the risk of exploitation.Fix
Incorrect Authorization
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Debian
Owasp Modsecurity Core Rule Set