Table of Contents
This issue affects the versions of curl as shipped with Red Hat Enterprise Linux 5, 6, and 7, as well as the versions of httpd24-curl as shipped with Red Hat Software Collections. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.
CVSS v3 metrics
|CVSS3 Base Score||4.3|
|CVSS3 Base Metrics||CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N|
Red Hat Security Errata
|Red Hat Enterprise Linux 7 (curl)||RHSA-2018:3157||2018-10-30|
|Red Hat Software Collections for Red Hat Enterprise Linux 6 (httpd24-curl)||RHSA-2018:3558||2018-11-13|
|Red Hat Software Collections for Red Hat Enterprise Linux 7 (httpd24-curl)||RHSA-2018:3558||2018-11-13|
Affected Packages State
|Red Hat JBoss Core Services 1||curl||Will not fix|
|Red Hat Enterprise Linux 6||curl||Will not fix|
|Red Hat Enterprise Linux 5||curl||Will not fix|
|Red Hat Ceph Storage 2||curl||Not affected|
|.NET Core 2.0 on Red Hat Enterprise Linux||rh-dotnet20-curl||Will not fix|
|.NET Core 2.0 on Red Hat Enterprise Linux||rh-dotnet21-curl||Will not fix|
|.NET Core 1.0 on Red Hat Enterprise Linux||rh-dotnetcore10-curl||Will not fix|
|.NET Core 1.0 on Red Hat Enterprise Linux||rh-dotnetcore11-curl||Will not fix|
AcknowledgementsRed Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges Craig de Stigter as the original reporter.
By default, curl and libcurl will not follow redirect requests.
This flaw happens only when curl or libcurl are explicitly requested to follow redirects (option --location in curl, and CURLOPT_FOLLOWLOCATION in libcurl).
To mitigate this, it is possible to prevent the automated following of redirects, replacing it by manual redirects (and remove the authentication header), for example.