curl before 7.53.0 has an incorrect TLS Certificate Status Request extension feature that asks for a fresh proof of the server's certificate's validity in the code that checks for a test success or failure. It ends up always thinking there's valid proof, even when there is none or if the server doesn't support the TLS extension in question. This could lead to users not detecting when a server's certificate goes invalid or otherwise be mislead that the server is in a better shape than it is in reality. This flaw also exists in the command line tool (--cert-status).
References
Link | Resource |
---|---|
https://curl.haxx.se/docs/adv_20170222.html | Vendor Advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2629 | Issue Tracking Patch Third Party Advisory |
https://www.tenable.com/security/tns-2017-09 | Third Party Advisory |
https://security.gentoo.org/glsa/201703-04 | Third Party Advisory |
http://www.securitytracker.com/id/1037871 | Third Party Advisory VDB Entry |
http://www.securityfocus.com/bid/96382 | Third Party Advisory VDB Entry |
Configurations
Information
Published : 2018-07-27 12:29
Updated : 2019-10-09 16:26
NVD link : CVE-2017-2629
Mitre link : CVE-2017-2629
JSON object : View
CWE
CWE-295
Improper Certificate Validation
Products Affected
haxx
- curl