curl's HSTS check could be bypassed to trick it to keep using HTTP.
Using its HSTS support, curl can be instructed to use HTTPS directly instead
of using an insecure clear-text HTTP step even when HTTP is provided in the
URL. This mechanism could be bypassed if the hostname in the given URL uses
IDN characters that get replaced to ASCII counterparts as part of the IDN
conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP
)
instead of the common ASCII full stop (U+002E) .
.
Like this: http://curl。se。
{ "CWE": { "id": "CWE-319", "desc": "Cleartext Transmission of Sensitive Information" }, "award": { "amount": "2400", "currency": "USD" }, "URL": "https://curl.se/docs/CVE-2022-42916.json", "package": "curl", "severity": "Medium", "issue": "https://hackerone.com/reports/1730660", "www": "https://curl.se/docs/CVE-2022-42916.html", "last_affected": "7.85.0" }