Loading HuntDB...
Hunt
Vulnerability Intelligence by wss.sh
Home Daily Briefings High Impact CVEs Recent Exploits KEV Catalog GitHub Advisories Latest Updates Security News
Sign In Sign Up

CVE-2017-2629

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

Expert Analysis

Professional remediation guidance

Get tailored security recommendations from our analyst team for CVE-2017-2629. We'll provide specific mitigation strategies based on your environment and risk profile.

CVSS Score

V3.0
4.3
/10
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Base Score Metrics
Exploitability: N/A Impact: N/A

EPSS Score

v2025.03.14
0.008
probability
of exploitation in the wild

There is a 0.8% chance that this vulnerability will be exploited in the wild within the next 30 days.

Updated: 2025-06-25
Exploit Probability
Percentile: 0.729
Higher than 72.9% of all CVEs

Attack Vector Metrics

Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
REQUIRED
Scope
UNCHANGED

Impact Metrics

Confidentiality
NONE
Integrity
LOW
Availability
NONE

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

Available Exploits

No exploits available for this CVE.

Related News

No news articles found for this CVE.

Affected Products

CURL

curl

Affected Versions:

7.53.0

GitHub Security Advisories

Community-driven vulnerability intelligence from GitHub

⚠ Unreviewed MODERATE

GHSA-7cp4-w7q7-w394

Advisory Details

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

CVSS Scoring

CVSS Score

5.0

CVSS Vector

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

References

ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2017-2629
WEB https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2629
WEB https://curl.haxx.se/docs/adv_20170222.html
WEB https://security.gentoo.org/glsa/201703-04
WEB https://www.tenable.com/security/tns-2017-09
WEB http://www.securityfocus.com/bid/96382
WEB http://www.securitytracker.com/id/1037871

Advisory provided by GitHub Security Advisory Database. Published: May 13, 2022, Modified: May 13, 2022

References

http://www.securityfocus.com/bid/96382
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2629
http://www.securitytracker.com/id/1037871
https://www.tenable.com/security/tns-2017-09
https://curl.haxx.se/docs/adv_20170222.html
https://security.gentoo.org/glsa/201703-04
Published: 2018-07-27T19:00:00
Last Modified: 2024-08-05T14:02:06.938Z
Copied to clipboard!