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.
The product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm.
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
| Link | Tags |
|---|---|
| https://hackerone.com/reports/1557449 | third party advisory exploit |
| https://security.netapp.com/advisory/ntap-20220609-0009/ | third party advisory |
| http://www.openwall.com/lists/oss-security/2022/10/26/4 | patch mailing list third party advisory |
| https://security.gentoo.org/glsa/202212-01 | third party advisory vendor advisory |
| http://www.openwall.com/lists/oss-security/2022/12/21/1 | third party advisory mailing list |