rclone: http backend forwards custom/auth headers to a different host on redirect
8Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 3.7epss 0.2%
exploitation probability
0.2%top 92% of all CVEs
observed exploitation
nono source reports it
rclone is a command-line program to sync files and directories to and from different cloud storage providers. From 1.49.0 until 1.75.1, the HTTP backend attaches headers configured through --http-headers or headers= to requests in backend/http/http.go, while its fshttp.NewClient client follows redirects without a backend-specific http.Client.CheckRedirect policy. A configured remote that redirects to another host can therefore cause custom secrets such as X-Api-Key to be resent to that untrusted destination, and a same-host HTTPS-to-HTTP redirect can expose Authorization or Cookie headers in cleartext. Listing, stat, download, mount, and serve operations can trigger the leak during normal use. This issue is fixed in version 1.75.1.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Affected products
rclone · rcloneReferences
https://github.com/rclone/rclone/commit/22859b7e696cea3c563c6ba04c6b7f91f74456b4https://github.com/rclone/rclone/commit/79fbc0842f74e02cb84f0e3e7261d169983c8831https://github.com/rclone/rclone/commit/925fb4fb21eb25e75cd1b64fdd17ded857784bfchttps://github.com/rclone/rclone/releases/tag/v1.75.1https://github.com/rclone/rclone/security/advisories/GHSA-486v-q2wf-fp2r