GHSA-w253-m66g-rx24: Coraza: URL-encoded form Content-Type parameters bypass Coraza body inspection
Coraza fails to inspect URL-encoded form bodies when their valid Content-Type contains a media-type parameter, for example:
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
An unauthenticated attacker can use this header to hide the complete form body from custom Coraza rules that inspect ARGS_POST or REQUEST_BODY, while the bundled Go HTTP middleware forwards the body and the backend parses it normally.
This is a deterministic request-body inspection bypass. Suggested severity: Medium. Current OWASP CRS includes rule 901340, which forces fallback inspection and mitigates this path; this report does not claim a bypass of an unmodified current CRS ruleset
References
- github.com/advisories/GHSA-w253-m66g-rx24
- github.com/corazawaf/coraza/commit/3b6241ef895b089c66a59e51068a81cf40986e4d
- github.com/corazawaf/coraza/commit/a55950ffa161f33a29e14f87d926d7df3b85cc74
- github.com/corazawaf/coraza/commit/dd100261cf1d2e2b053803a50c9db28dcaaa4b7c
- github.com/corazawaf/coraza/releases/tag/v3.8.1
- github.com/corazawaf/coraza/security/advisories/GHSA-w253-m66g-rx24
Code Behaviors & Features
Detect and mitigate GHSA-w253-m66g-rx24 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →