All reports
High

Git LFS may leak HTTP headers after redirections

Affected versions

Affected versions
>= 3.0.0, < 3.8.1
Fixed version
3.8.1
Affected versions
>= 0.5.0, <= 2.13.3
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Description

Impact

After receiving an HTTP redirection, Git LFS may forward certain HTTP headers to a host other than the one for which they were intended. While Authorization headers are never forwarded to inappropriate hosts, Cookie headers may be forwarded incorrectly.

Git LFS has resolved this issue by never forwarding Cookie headers to hosts other than the ones for which they were intended. In particular, after an HTTP redirection is received to a URL with a different scheme, host, or port than found in the URL of the current request, any Authorization and Cookie headers from the current request will not be sent in the redirected request.

Patches

This problem exists in all versions since 0.5.0 and is patched in v3.8.1. All users should upgrade to v3.8.1.

Workarounds

No single workaround exists. As far as possible, users and administrators should review their systems to confirm no unnecessary HTTP redirections are performed, and that HTTP headers other than Authorization do not contain privileged or confidential information.

For more information

If you have any questions or comments about this advisory:

Links

Credits

  • SnailSploit