Git LFS may leak HTTP headers after redirections
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in github.com/git-lfs/git-lfs/v3 3.8.1.
Git LFS is a Git extension for versioning large files. From 0.5.0 until 3.8.1, Git LFS may forward a Cookie header after an HTTP redirect to a host other than the one for which the header was intended. That unintended host can therefore receive cookies containing credentials or other confidential values. Authorization headers are never forwarded to inappropriate hosts and are not the affected secret in this vulnerability. This issue is fixed in version 3.8.1.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| git-lfs | >=0.5.0 <=2.13.3, >=3.0.0 <3.8.1 | ||
| go: github.com/git-lfs/git-lfs | >=0.5.0 <=2.13.3 | ||
| go: github.com/git-lfs/git-lfs/v3 | >=3.0.0 <3.8.1 | 3.8.1 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in github.com/git-lfs/git-lfs (Go), strongest first
Embed
A live severity badge for an advisory, README or ticket