CVE-2023-38199

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.

Category

9.8
CVSS
Severity: Critical
CVSS 3.1 •
EPSS 0.04%
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://github.com/coreruleset/coreruleset/issues/3191 patch issue tracking
https://github.com/coreruleset/coreruleset/pull/3237 issue tracking

Frequently Asked Questions

What is the severity of CVE-2023-38199?
CVE-2023-38199 has been scored as a critical severity vulnerability.
How to fix CVE-2023-38199?
To fix CVE-2023-38199, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2023-38199 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2023-38199 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.