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).
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published: 2018-07-27T19:00:00

Updated: 2024-08-05T14:02:06.938Z

Reserved: 2016-12-01T00:00:00

Link: CVE-2017-2629

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2018-07-27T19:29:00.440

Modified: 2019-10-09T23:26:59.053

Link: CVE-2017-2629

cve-icon Redhat

Severity : Moderate

Publid Date: 2017-02-22T00:00:00Z

Links: CVE-2017-2629 - Bugzilla