Name | 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. |
Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Debian Bugs | 1041109 |
Vulnerable and fixed packages
The table below lists information on source packages.
Source Package | Release | Version | Status |
---|
modsecurity-crs (PTS) | jessie | 2.2.9-1+deb8u1 | vulnerable |
| stretch (lts), stretch | 3.2.3-0+deb9u1 | vulnerable |
| buster (security), buster, buster (lts) | 3.2.3-0+deb10u3 | vulnerable |
| bullseye | 3.3.0-1+deb11u1 | vulnerable |
| bookworm | 3.3.4-1 | vulnerable |
| sid, trixie | 3.3.7-1 | fixed |
The information below is based on the following data on fixed versions.
Notes
[bookworm] - modsecurity-crs <no-dsa> (Minor issue)
[bullseye] - modsecurity-crs <no-dsa> (Minor issue)
[buster] - modsecurity-crs <postponed> (Minor issue)
https://github.com/coreruleset/coreruleset/issues/3191
https://github.com/coreruleset/coreruleset/pull/3237
[stretch] - modsecurity-crs <postponed> (Minor issue, Content-Type confusion)
[jessie] - modsecurity-crs <postponed> (Minor issue, Content-Type confusion)