Upstream information
Description
coreruleset (aka OWASP ModSecurity Core Rule Set) through 3.3.4 does not detect multiple Content-Type request headers on some platforms. This might allow attackers to bypass a WAF with a crafted payload, aka "Content-Type confusion" between the WAF and the backend application. This occurs when the web application relies on only the last Content-Type header. Other platforms may reject the additional Content-Type header or merge conflicting headers, leading to detection as a malformed header.SUSE information
Overall state of this security issue: Does not affect SUSE products
This issue is currently rated as having critical severity.
| CVSS detail | National Vulnerability Database | 
|---|---|
| Base Score | 9.8 | 
| Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | 
| Attack Vector | Network | 
| Attack Complexity | Low | 
| Privileges Required | None | 
| User Interaction | None | 
| Scope | Unchanged | 
| Confidentiality Impact | High | 
| Integrity Impact | High | 
| Availability Impact | High | 
| CVSSv3 Version | 3.1 | 
List of released packages
| Product(s) | Fixed package version(s) | References | 
|---|---|---|
| openSUSE Tumbleweed | 
  |  Patchnames:  openSUSE-Tumbleweed-2024-13187  | 
SUSE Timeline for this CVE
CVE page created: Thu Jul 13 06:02:46 2023CVE page last modified: Sat Nov 1 23:54:44 2025