VDB

CVE-2023-38199

CVE-2023-38199 PUBLISHED

Reported by mitre · Published July 13, 2023

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.

Affected products

VendorProductVersions
n/an/an/a
n/an/a*

Timeline

  • Jul 13, 2023 CVE Published
  • Jul 14, 2023 EPSS Score (30 in total, the first dated here)
  • Oct 30, 2024 CVE Updated
  • Jun 2, 2026 Security Advisory
  • Aug 6, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2023-38199
vulnetix vdb fixes CVE-2023-38199

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2023-38199/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›