Coreruleset
Approved changes feed: RSS · Atom
cpe:2.3:a:owasp:coreruleset:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Owasp (b778b703-6f88-5eeb-b966-330b456a6d00) |
|---|---|
| Product | Coreruleset (d25deb14-9e7c-5509-a45b-7f80406d4df4) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-38199 |
vulnerable | 2026-06-03 14:52:30.581848 |
Details available
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.
Published: 2023-07-13T00:00:00.000Z
Updated: 2024-10-30T18:55:24.723Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.