CVE-2017-2629
First published: Fri Jul 27 2018(Updated: )
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).
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Curl | <7.53.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-2629?
CVE-2017-2629 is rated as moderate in severity due to potential risks associated with TLS certificate validation.
How do I fix CVE-2017-2629?
To fix CVE-2017-2629, upgrade to curl version 7.53.0 or later where the vulnerability has been addressed.
What software is affected by CVE-2017-2629?
CVE-2017-2629 affects curl versions prior to 7.53.0.
What impact does CVE-2017-2629 have on system security?
CVE-2017-2629 may lead to an attacker being able to spoof server certificates, undermining TLS security.
Is CVE-2017-2629 a common vulnerability?
CVE-2017-2629 is one of several vulnerabilities discovered in common applications that use TLS for secure communication.
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/remedy
- agent/severity
- agent/last-modified-date
- agent/weakness
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/haxx
- canonical/curl