CVE-2017-2629
mediumpriority · track · 26EPSS 0.012 · 69 %ileDEEUUSEPSS · scored 2026-10-27
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).
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (4)
Products and version ranges known to be affected.
advisories (3)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2023-1649cURL: Schwachstelle ermöglicht Umgehen von SicherheitsvorkehrungenDeutsch2017-02-21csaf · cert_bundDE
Ein entfernter, anonymer Angreifer kann eine Schwachstelle in cURL ausnutzen, um Sicherheitsvorkehrungen zu umgehen.
- WID-SEC-W-2026-0180Dell Data Protection Advisor: Mehrere SchwachstellenDeutsch2026-01-20csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in Dell Data Protection Advisor ausnutzen, um beliebigen Code auszuführen, einen Denial-of-Service-Zustand zu erzeugen, Sicherheitsmaßnahmen zu umgehen und nicht näher spezifizierte Angriffe zu starten.
- CURL-CVE-2017-2629SSL_VERIFYSTATUS ignored2017-02-22vendor · osvUS
curl and libcurl support "OCSP stapling", also known as the TLS Certificate Status Request extension (using the `CURLOPT_SSL_VERIFYSTATUS` option). When telling curl to use this feature, it uses that TLS extension to ask for a fresh proof of the server's certificate's validity. If the server does not support the extension, or fails to provide said proof, curl is expected to return an error. Due to a coding mistake, the code that checks for a test success or failure, ends up always thinking there is valid proof, even when there is none or if the server does not support the TLS extension in question. Contrary to how it used to function and contrary to how this feature is documented to work. 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](https://curl.se/docs/manpage.html#--cert-status)).
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (18)
External citations — patches, advisories, analysis.
- http://www.securitytracker.com/id/1037871cnnvd
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2629cnnvd
- https://curl.haxx.se/docs/adv_20170222.htmlcnnvd
- https://security.gentoo.org/glsa/201703-04cnnvd
- https://www.securityfocus.com/bid/96382cnnvd
- https://www.tenable.com/security/tns-2017-09cnnvd
- http://www.securityfocus.com/bid/96382enisa_euvd
- http://www.securitytracker.com/id/1037871enisa_euvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan