CVE-2017-2629

medium

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

References

https://www.tenable.com/security/tns-2017-09

https://security.gentoo.org/glsa/201703-04

https://curl.haxx.se/docs/adv_20170222.html

https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2629

http://www.securitytracker.com/id/1037871

http://www.securityfocus.com/bid/96382

Details

Source: Mitre, NVD

Published: 2018-07-27

Updated: 2019-10-09

Risk Information

CVSS v2

Base Score: 4

Vector: CVSS2#AV:N/AC:L/Au:S/C:N/I:P/A:N

Severity: Medium

CVSS v3

Base Score: 6.5

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Severity: Medium