CVE-2023-38199: Critical severity OWASP coreruleset vulnerability

Published Jul 13, 2023
·
Updated

coreruleset (aka OWASP ModSecurity Core Rule Set) through 3.3.4 does not block multiple Content-Type headers, which might allow attackers to bypass a WAF with a crafted payload, aka "Content-Type confusion." This occurs when the web application relies on only the last Content-Type header.

Other sources

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 Software

1 affected component
OWASP coreruleset<=3.3.4

Event History

Jul 13, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
03:15 AM
Description
Data Sourced
via NVD·03:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2023-38199?

CVE-2023-38199 is a vulnerability in coreruleset (aka OWASP ModSecurity Core Rule Set) through version 3.3.4 that allows attackers to bypass a Web Application Firewall (WAF) by using multiple Content-Type request headers.

2

What is the severity of CVE-2023-38199?

CVE-2023-38199 has a severity level of critical with a severity value of 9.8.

3

How does CVE-2023-38199 affect coreruleset?

CVE-2023-38199 affects coreruleset (aka OWASP ModSecurity Core Rule Set) through version 3.3.4 by allowing attackers to bypass the WAF with a crafted payload using multiple Content-Type request headers.

4

Is there a fix for CVE-2023-38199?

As of now, there is no fix available for CVE-2023-38199. It is recommended to follow the official GitHub issue and pull request for updates.

5

What is the Common Weakness Enumeration (CWE) ID for CVE-2023-38199?

The CWE ID for CVE-2023-38199 is CWE-843.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203