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.
References
Link | Resource |
---|---|
https://hackerone.com/reports/1553841 | Exploit Third Party Advisory |
https://security.netapp.com/advisory/ntap-20220609-0009/ | Third Party Advisory |
https://security.gentoo.org/glsa/202212-01 | 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:57
NVD link : CVE-2022-27780
Mitre link : CVE-2022-27780
JSON object : View
CWE
CWE-918
Server-Side Request Forgery (SSRF)
Products Affected
netapp
- hci_compute_node
- clustered_data_ontap
- h500s
- h300s
- h500s_firmware
- solidfire_\&_hci_management_node
- h700s
- solidfire\,_enterprise_sds_\&_hci_storage_node
- hci_bootstrap_os
- h410s_firmware
- h300s_firmware
- h700s_firmware
- h410s
haxx
- curl