Coraza upload filename rule bypass in multipart parsing
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 before 3.8.1 extracts multipart upload filenames with Go's mime.ParseMediaType, which silently ignores RFC 5987 filename* parameters whose charset is not utf-8 or us-ascii. Unauthenticated attackers can send a decoy filename with filename*=iso-8859-1''shell.php, or filename* alone, so FILES-based rules never see the real name, letting dangerous uploads reach backends that honor filename*.
From the CVE record · VulnCheck
Coraza before 3.8.1 can ignore multipart filename* parameters that use charsets other than UTF-8 or US-ASCII. An unauthenticated attacker can submit an upload whose filename evades FILES-based rules, allowing dangerous files to reach backends that honor filename*.
Check deployments using Go packages github.com/corazawaf/coraza/v3 before 3.8.1, or any version of github.com/corazawaf/coraza or github.com/corazawaf/coraza/v2.