First published: Mon Aug 01 2016(Updated: )
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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/curl | <0:7.29.0-35.el7 | 0:7.29.0-35.el7 |
redhat/httpd24-curl | <0:7.61.1-1.el6 | 0:7.61.1-1.el6 |
redhat/httpd24-httpd | <0:2.4.34-7.el6 | 0:2.4.34-7.el6 |
redhat/httpd24-nghttp2 | <0:1.7.1-7.el6 | 0:1.7.1-7.el6 |
redhat/httpd24-curl | <0:7.61.1-1.el7 | 0:7.61.1-1.el7 |
redhat/httpd24-httpd | <0:2.4.34-7.el7 | 0:2.4.34-7.el7 |
redhat/httpd24-nghttp2 | <0:1.7.1-7.el7 | 0:1.7.1-7.el7 |
redhat/curl | <7.50.1 | 7.50.1 |
Android | ||
Debian Linux | =8.0 | |
libcurl | <=7.50.0 | |
SUSE Linux | =42.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
CVE-2016-5420 has been classified as a medium severity vulnerability.
To address CVE-2016-5420, upgrade curl and libcurl to version 7.50.1 or later.
CVE-2016-5420 affects curl and libcurl versions prior to 7.50.1 across various distributions.
Yes, CVE-2016-5420 may allow remote attackers to hijack authentication of connections.
CVE-2016-5420 involves a vulnerability in the TLS connection mechanism related to client certificates.