|From:||Pat Riehecky <firstname.lastname@example.org>|
|Subject:||Security ERRATA Moderate: curl on SL6.x i386/x86_64|
|Date:||Tue, 27 May 2014 18:10:33 +0000|
Synopsis: Moderate: curl security and bug fix update Advisory ID: SLSA-2014:0561-1 Issue Date: 2014-05-27 CVE Numbers: CVE-2014-0015 CVE-2014-0138 -- It was found that libcurl could incorrectly reuse existing connections for requests that should have used different or no authentication credentials, when using one of the following protocols: HTTP(S) with NTLM authentication, LDAP(S), SCP, or SFTP. If an application using the libcurl library connected to a remote server with certain authentication credentials, this flaw could cause other requests to use those same credentials. (CVE-2014-0015, CVE-2014-0138) This update also fixes the following bugs: * Previously, the libcurl library was closing a network socket without first terminating the SSL connection using the socket. This resulted in a write after close and consequent leakage of memory dynamically allocated by the SSL library. An upstream patch has been applied on libcurl to fix this bug. As a result, the write after close no longer happens, and the SSL library no longer leaks memory. * Previously, the libcurl library did not implement a non-blocking SSL handshake, which negatively affected performance of applications based on libcurl's multi API. To fix this bug, the non-blocking SSL handshake has been implemented by libcurl. With this update, libcurl's multi API immediately returns the control back to the application whenever it cannot read/write data from/to the underlying network socket. * Previously, the curl package could not be rebuilt from sources due to an expired cookie in the upstream test-suite, which runs during the build. An upstream patch has been applied to postpone the expiration date of the cookie, which makes it possible to rebuild the package from sources again. * Previously, the libcurl library attempted to authenticate using Kerberos whenever such an authentication method was offered by the server. This caused problems when the server offered multiple authentication methods and Kerberos was not the selected one. An upstream patch has been applied on libcurl to fix this bug. Now libcurl no longer uses Kerberos authentication if another authentication method is selected. All running applications that use libcurl have to be restarted for this update to take effect. -- SL6 x86_64 curl-7.19.7-37.el6_5.3.x86_64.rpm curl-debuginfo-7.19.7-37.el6_5.3.i686.rpm curl-debuginfo-7.19.7-37.el6_5.3.x86_64.rpm libcurl-7.19.7-37.el6_5.3.i686.rpm libcurl-7.19.7-37.el6_5.3.x86_64.rpm libcurl-devel-7.19.7-37.el6_5.3.i686.rpm libcurl-devel-7.19.7-37.el6_5.3.x86_64.rpm i386 curl-7.19.7-37.el6_5.3.i686.rpm curl-debuginfo-7.19.7-37.el6_5.3.i686.rpm libcurl-7.19.7-37.el6_5.3.i686.rpm libcurl-devel-7.19.7-37.el6_5.3.i686.rpm - Scientific Linux Development Team
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds