VDB

CVE-2016-5420

CVE-2016-5420 PUBLISHED

Reported by redhat · Published August 10, 2016

curl and libcurl before 7.50.1 do not check the client certificate when choosing the TLS connection to reuse, which might allow remote attackers to hijack the authentication of the connection by leveraging a previously created connection with a different client certificate.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
curlUbuntu:14.04:LTS7.35.0-1ubuntu2.8
libcurlhaxx7.50.0

Affected products

VendorProductVersions
n/an/an/a
n/an/a*
alpinecurl0, 0, 0

Timeline

  • Aug 10, 2016 CVE Published
  • Feb 4, 2022 EPSS Score (30 in total, the first dated here)
  • Mar 5, 2026 Distribution Patch (4 in total, the first dated here)
  • Mar 5, 2026 Security Advisory (7 in total, the first dated here)
  • Oct 7, 2026 Coalition ESS Score
  • Oct 14, 2026 PoC Published

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2016-5420
vulnetix vdb fixes CVE-2016-5420

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2016-5420/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›