Improper Certificate Validation Affecting curl package, versions <7.53.0-r0
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-ALPINE316-CURL-2841963
- published 27 Jun 2018
- disclosed 27 Jul 2018
Introduced: 27 Jun 2018
CVE-2017-2629 Open this link in a new tabHow to fix?
Upgrade Alpine:3.16
curl
to version 7.53.0-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl
package and not the curl
package as distributed by Alpine
.
See How to fix?
for Alpine:3.16
relevant fixed versions and status.
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
- https://curl.haxx.se/docs/adv_20170222.html
- https://www.tenable.com/security/tns-2017-09
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2629
- https://security-tracker.debian.org/tracker/CVE-2017-2629
- https://security.gentoo.org/glsa/201703-04
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2629
- http://www.securityfocus.com/bid/96382
- http://www.securitytracker.com/id/1037871