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.
lists.opensuse.org/opensuse-updates/2016-09/msg00011.html
lists.opensuse.org/opensuse-updates/2016-09/msg00094.html
rhn.redhat.com/errata/RHSA-2016-2575.html
rhn.redhat.com/errata/RHSA-2016-2957.html
www.debian.org/security/2016/dsa-3638
www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html
www.securityfocus.com/bid/92309
www.securitytracker.com/id/1036537
www.securitytracker.com/id/1036739
www.slackware.com/security/viewer.php?l=slackware-security&y=2016&m=slackware-security.563059
www.ubuntu.com/usn/USN-3048-1
access.redhat.com/errata/RHSA-2018:3558
curl.haxx.se/docs/adv_20160803B.html
lists.fedoraproject.org/archives/list/[email protected]/message/GLPXQQKURBQFM4XM6645VRPTOE2AWG33/
lists.fedoraproject.org/archives/list/[email protected]/message/K3GQH4V3XAQ5Z53AMQRDEC3C3UHTW7QR/
security.gentoo.org/glsa/201701-47
source.android.com/security/bulletin/2016-12-01.html
www.tenable.com/security/tns-2016-18