CVE-2023-38199
This might allow attackers to bypass a WAF with a crafted payload, aka "Content-Type confusion" between the WAF and the backend application.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.75%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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.
- CVSS 3.1
- 9.8 CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 0.75% probability · 53th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-843
- Affected
- owasp/coreruleset
- Source
- cve@mitre.org
References
- https://github.com/coreruleset/coreruleset/issues/3191Issue Tracking, Patch
- https://github.com/coreruleset/coreruleset/pull/3237Issue Tracking
- https://github.com/coreruleset/coreruleset/issues/3191Issue Tracking, Patch
- https://github.com/coreruleset/coreruleset/pull/3237Issue Tracking
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.