CVE-2016-5419: High severity Google Android vulnerability
curl and libcurl before 7.50.1 do not prevent TLS session resumption when the client certificate has changed, which allows remote attackers to bypass intended restrictions by resuming a session.
Other sources
It was reported that libcurl would attempt to resume a TLS session even if the client certificate had changed. That is unacceptable since a server by specification is allowed to skip the client certificate check on resume, and may instead use the old identity which was established by the previous certificate (or no certificate).
libcurl supports by default the use of TLS session id/ticket to resume previous TLS sessions to speed up subsequent TLS handshakes. They are used when for any reason an existing TLS connection couldn't be kept alive to make the next handshake faster.
External Reference:
https://curl.haxx.se/docs/adv20160803A.html
— Red Hat
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2016-5419?
CVE-2016-5419 is categorized as a medium severity vulnerability.
How do I fix CVE-2016-5419?
To fix CVE-2016-5419, update curl and libcurl to version 7.50.1 or newer.
What does CVE-2016-5419 affect?
CVE-2016-5419 affects curl and libcurl versions prior to 7.50.1.
What kind of attack does CVE-2016-5419 allow?
CVE-2016-5419 allows remote attackers to bypass security restrictions by resuming a TLS session with a changed client certificate.
Is CVE-2016-5419 present in Debian Linux?
Yes, CVE-2016-5419 is present in Debian GNU/Linux 8.0 and needs to be addressed by updating the software.