DEBIAN-CVE-2017-2629

Source
https://security-tracker.debian.org/tracker/CVE-2017-2629
Import Source
https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2017-2629.json
JSON Data
https://api.test.osv.dev/v1/vulns/DEBIAN-CVE-2017-2629
Upstream
Published
2018-07-27T19:29:00Z
Modified
2025-09-19T06:15:15Z
Summary
[none]
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).

References

Affected packages

Debian:11 / curl

Package

Name
curl
Purl
pkg:deb/debian/curl?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
7.52.1-3

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:12 / curl

Package

Name
curl
Purl
pkg:deb/debian/curl?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
7.52.1-3

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:13 / curl

Package

Name
curl
Purl
pkg:deb/debian/curl?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
7.52.1-3

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:14 / curl

Package

Name
curl
Purl
pkg:deb/debian/curl?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
7.52.1-3

Ecosystem specific

{
    "urgency": "not yet assigned"
}