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.
References
Link | Resource |
---|---|
https://hackerone.com/reports/1557449 | Exploit Third Party Advisory |
https://security.netapp.com/advisory/ntap-20220609-0009/ | Third Party Advisory |
http://www.openwall.com/lists/oss-security/2022/10/26/4 | Mailing List Patch Third Party Advisory |
https://security.gentoo.org/glsa/202212-01 | Third Party Advisory |
http://www.openwall.com/lists/oss-security/2022/12/21/1 | Mailing List Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
AND |
|
Configuration 3 (hide)
|
Configuration 4 (hide)
AND |
|
Configuration 5 (hide)
AND |
|
Configuration 6 (hide)
AND |
|
Configuration 7 (hide)
AND |
|
Information
Published : 2022-06-02 07:15
Updated : 2023-01-05 09:50
NVD link : CVE-2022-30115
Mitre link : CVE-2022-30115
JSON object : View
CWE
CWE-319
Cleartext Transmission of Sensitive Information
Products Affected
netapp
- hci_compute_node
- clustered_data_ontap
- h300s
- h500s
- h500s_firmware
- solidfire_\&_hci_management_node
- h700s
- solidfire\,_enterprise_sds_\&_hci_storage_node
- hci_bootstrap_os
- h410s_firmware
- h410s
- h700s_firmware
- h300s_firmware
haxx
- curl