Cleartext Transmission of Sensitive Information Affecting libcurl package, versions *
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-CENTOS6-LIBCURL-2814388
- published 11 May 2022
- disclosed 11 May 2022
Introduced: 11 May 2022
CVE-2022-30115 Open this link in a new tabHow to fix?
There is no fixed version for Centos:6 libcurl.
NVD Description
Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Centos.
See How to fix? for Centos:6 relevant fixed versions and status.
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
- https://access.redhat.com/security/cve/CVE-2022-30115
- https://hackerone.com/reports/1557449
- https://security.netapp.com/advisory/ntap-20220609-0009/
- http://www.openwall.com/lists/oss-security/2022/10/26/4
- https://security.gentoo.org/glsa/202212-01
- http://www.openwall.com/lists/oss-security/2022/12/21/1