CVE-2017-2629
Last modified
CVE-2017-2629 is a medium-severity vulnerability rated 4.3/10 on the CVSS scale. 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. EPSS estimates a 1.39% chance of exploitation in the next 30 days.
Description
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).
Metrics
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Haxx | Curl | < 7.53.0 |
References
- http://www.securityfocus.com/bid/96382Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1037871Third Party Advisory, VDB Entry
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2629Issue Tracking, Patch, Third Party Advisory
- https://curl.haxx.se/docs/adv_20170222.htmlVendor Advisory
- https://security.gentoo.org/glsa/201703-04Third Party Advisory
- https://www.tenable.com/security/tns-2017-09Third Party Advisory
- http://www.securityfocus.com/bid/96382Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1037871Third Party Advisory, VDB Entry
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2629Issue Tracking, Patch, Third Party Advisory
- https://curl.haxx.se/docs/adv_20170222.htmlVendor Advisory
- https://security.gentoo.org/glsa/201703-04Third Party Advisory
- https://www.tenable.com/security/tns-2017-09Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-2629?
How severe is CVE-2017-2629?
How do I fix CVE-2017-2629?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-2623It was discovered that rpm-ostree and rpm-ostree-client befo…5.3
- CVE-2017-2624It was found that xorg-x11-server before 1.19.0 including us…5.9
- CVE-2017-2625It was discovered that libXdmcp before 1.1.2 including used …6.5
- CVE-2017-2626It was discovered that libICE before 1.0.9-8 used a weak ent…5.2
- CVE-2017-2627A flaw was found in openstack-tripleo-common as shipped with…8.2
- CVE-2017-2628curl, as shipped in Red Hat Enterprise Linux 6 before versio…
- CVE-2017-2630A stack buffer overflow flaw was found in the Quick Emulator…5.5
- CVE-2017-2631Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2017-2632A logic error in valid_role() in CloudForms role validation …4.9
- CVE-2017-2633An out-of-bounds memory access issue was found in Quick Emul…5.4
- CVE-2017-2634It was found that the Linux kernel's Datagram Congestion Con…7.5
- CVE-2017-2635A NULL pointer deference flaw was found in the way libvirt f…7.7
Are you affected by CVE-2017-2629?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
