# CVE-2017-2629: Security feature bypass in curl

> curl fails to properly validate TLS certificate status, allowing attackers to bypass certificate revocation checks and mislead users about server validity.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-2629, CLEANSTART-2026-XS69927, CURL-CVE-2017-2629, DEBIAN-CVE-2017-2629, GHSA-7cp4-w7q7-w394

## What is CVE-2017-2629?

CVE-2017-2629 is a medium-severity vulnerability in Haxx Curl, published on 27 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

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

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2017-2629?

It affects 1 product.


Products: Haxx Curl.

## How do I fix CVE-2017-2629?

Upgrade to a fixed version.

## Is CVE-2017-2629 being exploited?

There is no known exploitation of CVE-2017-2629 in the wild and no public exploit code.

## Other vulnerabilities in Haxx Curl

- [CVE-2026-19931](https://insights.sbomify.com/CVE-2026-19931/): Negotiate ambient user conn reuse (critical 9.8)
- [CVE-2026-10536](https://insights.sbomify.com/CVE-2026-10536/): HTTP/2 stream-dependency tree UAF (critical 9.8)
- [CVE-2026-11856](https://insights.sbomify.com/CVE-2026-11856/): cross-origin Digest auth state leak (critical 9.8)
- [CVE-2026-8925](https://insights.sbomify.com/CVE-2026-8925/): SASL double-free (critical 9.8)
- [CVE-2026-9079](https://insights.sbomify.com/CVE-2026-9079/): stale proxy password leak (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-2629 and fix it if it is affected.

What it is: CVE-2017-2629 is a medium-severity vulnerability in Haxx Curl, published on 27 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-2629 in the wild and no public exploit code.

Affected product: Haxx Curl. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-2629/ (Markdown: https://insights.sbomify.com/CVE-2017-2629/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-2629
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-2629
- OSV: https://osv.dev/vulnerability/CVE-2017-2629

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-2629/
Summaries are generated and may contain mistakes; the official description above is the record.