4.3med

CVE-2017-2629

curl before 7.53.0 has an incorrect TLS Certificate Status Request extension feature that asks for a fresh proof of the server's certificat…

Published 8 y ago · modified 4 mo ago · JSON

CVSS
4.3
v3.0 · CNA
CISA KEV
No
not known exploited
EPSS
1.2%
percentile 69%
Public exploits
0
none known

Summary

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

Exploit prediction (EPSS)

1.23% probability of exploitation in the next 30 days, higher than 69% of all scored CVEs.

CVSS scores

Assigned byVersionScoreVector
CNA3.04.3CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
CNA3.04.3CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
NVD3.06.5CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
NVD2.04.0AV:N/AC:L/Au:S/C:N/I:P/A:N

Affected products

  • CURL curl

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

vulnwire keeps one entry per vulnerability: the CVE id wins, then GHSA; records that alias each other are merged. Machine-readable: JSON.