Coraza SQL injection rule bypass via JSON property collisions
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.0 before 3.8.1 has a JSON body processor that flattens nested properties into dot-separated ARGS_POST names without escaping literal dots, so distinct properties collide. Unauthenticated attackers can add a later dotted property such as account.role that overwrites a malicious nested value, hiding SQL injection payloads from OWASP CRS rules while backends still receive them.
From the CVE record · VulnCheck
Coraza's JSON body processor does not escape literal dots when flattening nested properties into ARGS_POST names, causing distinct properties to collide. An unauthenticated attacker can use a later dotted property to hide a SQL injection payload from OWASP CRS rules while the backend still receives it.
Check Go applications using github.com/corazawaf/coraza/v3 versions 3.0.0 through 3.8.0, or any version of github.com/corazawaf/coraza or github.com/corazawaf/coraza/v2.