Medium · published June 2, 2022
Using its HSTS support, curl can be instructed to use HTTPS directly insteadof using an insecure clear-text HTTP step even when HTTP is provided in theURL. This mechanism could be bypassed if the host name in the given URL used atrailing dot while not using one when it built the HSTS cache. Or the otherway around - by having the trailing dot in the HSTS cache and *not* using thetrailing dot in the URL.
| Product | Versions | Fixed in |
|---|---|---|
| haxx/curl | ≥ 7.82.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/h300s_firmware | all versions | — |
| netapp/h500s_firmware | all versions | — |
| netapp/h700s_firmware | all versions | — |
| netapp/h410s_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 | — |