Coraza request body inspection bypass via Content-Type parameters
corazawaf coraza
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/corazawaf/coraza/v3 Go |
|
|
| github.com/corazawaf/coraza Go |
| No fix yet |
| github.com/corazawaf/coraza/v2 Go |
|
corazawaf coraza
| Product | Affected | Fixed in |
|---|---|---|
| github.com/corazawaf/coraza/v3 Go |
|
|
| github.com/corazawaf/coraza Go |
| No fix yet |
| github.com/corazawaf/coraza/v2 Go |
|
| No fix yet |
Coraza from 3.0.4 before 3.8.1 contains a request body inspection bypass because request-body processor selection compares the entire Content-Type value exactly, so URL-encoded bodies whose Content-Type carries a media-type parameter are never parsed. Unauthenticated attackers can send application/x-www-form-urlencoded; charset=UTF-8 to keep ARGS_POST and REQUEST_BODY empty, evading body rules while the backend still processes the payload.
From the CVE record · VulnCheck
Coraza compares the full Content-Type value when selecting a request-body processor, so URL-encoded bodies with a media-type parameter are not parsed. An unauthenticated attacker can send a request with `Content-Type: application/x-www-form-urlencoded; charset=UTF-8` to leave `ARGS_POST` and `REQUEST_BODY` empty and evade body rules while the backend processes the payload.
Engineers running Go package `github.com/corazawaf/coraza/v3` versions 3.0.4 to before 3.8.1, or any version of `github.com/corazawaf/coraza` or `github.com/corazawaf/coraza/v2`, should check their deployments.