View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005421 | Kali Linux | Kali Websites & Docs | public | 2019-05-01 16:40 | 2025-07-14 09:37 |
| Reporter | elrey | Assigned To | rhertzog | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Summary | 0005421: Issue with WAF blocking curl/wget requests to https://www.kali.org/archive-key.asc | ||||
| Description | I think that your current WAF is treating curl and wget as malicious traffic, and I figured this out, because if you look at the picture attached called "curl_w_without_burp-proxy.png" the only difference between those two calls is that I am proxying my traffic through burp. So instead of it fingerprinting what is viewing it as curl it thinks it is some type of web browser. Which is why in the first call I am getting garbage (i.e. binary output, which you can see in the picture "curl_binary_output.png"), and the second is the regular key output. | ||||
| Steps To Reproduce | |||||
| Additional Information | curl versions tested with: 7.64.0, 7.52.1 I figured this out because of my automation project: http://github.com/elreydetoda/packer-kali_linux | ||||
| Attached Files | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-05-01 16:40 | elrey | New Issue | |
| 2019-05-01 16:40 | elrey | File Added: curl_w_without_burp-proxy.png | |
| 2019-05-01 16:40 | elrey | File Added: curl_binary_output.png | |
| 2019-05-01 16:47 | elrey | File Added: curl_fixed.png | |
| 2019-05-01 16:47 | elrey | Note Added: 0010547 | |
| 2019-05-03 06:31 | rhertzog | Assigned To | => rhertzog |
| 2019-05-03 06:31 | rhertzog | Status | new => closed |
| 2019-05-03 06:31 | rhertzog | Resolution | open => no change required |
| 2019-05-03 06:31 | rhertzog | Note Added: 0010556 | |
| 2025-07-14 09:37 | g0tmi1k | Severity | block => minor |