High · published June 2, 2022
The curl URL parser wrongly accepts percent-encoded URL separators like '/'when decoding the host name part of a URL, making it a *different* URL usingthe wrong host name when it is later retrieved.For example, a URL like `http://example.com%2F127.0.0.1/`, would be allowed bythe parser and get transposed into `http://example.com/127.0.0.1/`. This flawcan be used to circumvent filters, checks and more.
| Product | Versions | Fixed in |
|---|---|---|
| haxx/curl | ≥ 7.80.0, < 7.83.1 | 7.83.1 |
| netapp/hci_bootstrap_os | all versions | — |
| netapp/clustered_data_ontap | all versions | — |
| netapp/solidfire\,_enterprise_sds_\&_hci_storage_node | all versions | — |
| netapp/solidfire_\&_hci_management_node | all versions | — |
| netapp/h410s_firmware | all versions | — |
| netapp/h700s_firmware | all versions | — |
| netapp/h500s_firmware | all versions | — |
| netapp/h300s_firmware | all versions | — |
| splunk/universal_forwarder | ≥ 8.2.0, < 8.2.12 | 8.2.12 |
| splunk/universal_forwarder | ≥ 9.0.0, < 9.0.6 | 9.0.6 |
| splunk/universal_forwarder | all versions | — |