Dalfox: Unauthenticated Remote DoS via Closed-Channel Write in `ParameterAnalysis` (server mode)
hahwul dalfox
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/hahwul/dalfox/v2 Go |
|
|
| github.com/hahwul/dalfox Go |
| No fix yet |
hahwul dalfox
| Product | Affected | Fixed in |
|---|---|---|
| github.com/hahwul/dalfox/v2 Go |
|
|
| github.com/hahwul/dalfox Go |
| No fix yet |
Dalfox is a powerful open-source XSS scanner and utility focused on automation. Prior to 2.13.0, ParameterAnalysis in pkg/scanning/parameterAnalysis.go runs two sequential worker stages that both write to the same results channel. The channel is correctly closed after the first stage completes (close(results) at line 438), but the second stage — which processes POST-body parameters (dp) — is then launched with the same already-closed channel as its output. When a scanned parameter is reflected, processParams executes results <- paramResult on the closed channel, triggering a Go runtime panic that crashes the entire dalfox process. In server mode, the crash is remotely triggerable by any unauthenticated caller who can reach the REST API, because the default configuration has no API key and the second stage activates whenever options.Data != "" (i.e., the attacker supplies the data field) and the target reflects at least one parameter. This vulnerability is fixed in 2.13.0.
From the CVE record · GitHub_M
Dalfox versions before 2.13.0 can panic when POST-body parameter analysis writes a reflected result to a closed channel. In server mode with the default configuration, an unauthenticated remote caller can crash the process through the REST API by supplying the data field when the target reflects a parameter.
Teams running Go package github.com/hahwul/dalfox/v2 before 2.13.0 or github.com/hahwul/dalfox at any version should check their deployments.