Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
First Last Prev Next    This bug is not in your last search results.
Bug 1362183 - (CVE-2016-5419) CVE-2016-5419 curl: TLS session resumption client cert bypass
CVE-2016-5419 curl: TLS session resumption client cert bypass
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20160803,repor...
: Security
Depends On: 1363644 1363642 1363643 1364910 1367871
Blocks: 1362200 1395463
  Show dependency tree / graph
 
Reported: 2016-08-01 09:18 EDT by Adam Mariš
Modified: 2018-07-18 10:58 EDT (History)
26 users (show)

See Also:
Fixed In Version: curl 7.50.1
Doc Type: Bug Fix
Doc Text:
It was found that the libcurl library did not prevent TLS session resumption when the client certificate had changed. An attacker could potentially use this flaw to hijack the authentication of the connection by leveraging a previously created connection with a different client certificate.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2575 normal SHIPPED_LIVE Moderate: curl security, bug fix, and enhancement update 2016-11-03 08:06:39 EDT
Red Hat Product Errata RHSA-2016:2957 normal SHIPPED_LIVE Important: Red Hat JBoss Core Services Apache HTTP 2.4.23 Release 2016-12-15 22:11:19 EST

  None (edit)
Description Adam Mariš 2016-08-01 09:18:54 EDT 
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/adv_20160803A.html
Comment 1 Adam Mariš 2016-08-03 05:24:35 EDT 
Created curl tracking bugs for this issue:

Affects: fedora-all [bug 1363642]
Comment 2 Adam Mariš 2016-08-03 05:24:46 EDT 
Created mingw-curl tracking bugs for this issue:

Affects: fedora-all [bug 1363643]
Affects: epel-7 [bug 1363644]
Comment 3 Fedora Update System 2016-08-05 16:52:38 EDT 
curl-7.47.1-6.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
Comment 5 Fedora Update System 2016-08-16 18:21:16 EDT 
curl-7.43.0-8.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
Comment 9 errata-xmlrpc 2016-11-03 13:44:52 EDT 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2016:2575 https://rhn.redhat.com/errata/RHSA-2016-2575.html
Comment 11 errata-xmlrpc 2016-12-15 17:11:44 EST 
This issue has been addressed in the following products:



Via RHSA-2016:2957 https://rhn.redhat.com/errata/RHSA-2016-2957.html
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.