Vulnerability Details : CVE-2023-38199
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.
Products affected by CVE-2023-38199
- cpe:2.3:a:owasp:coreruleset:*:*:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2023-38199
0.17%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 54 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2023-38199
Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
---|---|---|---|---|---|---|
9.8
|
CRITICAL | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
3.9
|
5.9
|
NIST |
CWE ids for CVE-2023-38199
-
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.Assigned by: nvd@nist.gov (Primary)
References for CVE-2023-38199
-
https://github.com/coreruleset/coreruleset/pull/3237
feat: new rule 920620 by theMiddleBlue · Pull Request #3237 · coreruleset/coreruleset · GitHubIssue Tracking
-
https://github.com/coreruleset/coreruleset/issues/3191
Fix C9K-230327 · Issue #3191 · coreruleset/coreruleset · GitHubIssue Tracking;Patch
Jump to