GHSA-X7XJ-4J4F-88XR
Git LFS may leak HTTP headers after redirections
Texto original en inglés · Ver en español
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche v3.8.1 | github.com/git-lfs/git-lfs/v3 · -30 d desde divulgación | |
| Monitoreo | Detectada | Ingresó al índice | |
| Divulgación | Publicada | GHSA-X7XJ-4J4F-88XR divulgada · CVSS 7.6 (GitHub) | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Fuente: GitHub Security Advisories | Registro visto por primera vez en GitHub Security Advisories | |
| Monitoreo | Fuente: OSV | Registro visto por primera vez en OSV | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
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:
* For general questions, start a discussion in the Git LFS discussion forum https://github.com/git-lfs/git-lfs/discussions.
* For reports of additional vulnerabilities, please follow the Git LFS security reporting policy https://github.com/git-lfs/git-lfs/blob/main/SECURITY.md.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogithub.com/git-lfs/git-lfs |
Sin parche | — | — | v2.5.2+incompatible afectada |
gogithub.com/git-lfs/git-lfs/v3 |
Corregida | v3.8.1 | -30 d | v3.8.1 no afectada |
3.8.1v3.8.1Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://nvd.nist.gov/vuln/detail/CVE-2026-69261https://github.com/git-lfs/git-lfs/security/advisories/GHSA-x7xj-4j4f-88xrhttps://github.com/git-lfs/git-lfs/commit/12c92e05b3433494d4b8695943e7e230744d77d9https://github.com/git-lfs/git-lfs/commit/256d371024e6d2cf19efe675d8b9ad089785d0a1https://github.com/git-lfs/git-lfs/commit/537203a1fa08fdde4c16288fb039174ff0e692bbhttps://github.com/git-lfs/git-lfs/commit/d65324a7d5104c7a5dcb8c4959933695c8bc10fahttps://github.com/git-lfs/git-lfshttps://github.com/git-lfs/git-lfs/releases/tag/v3.8.1Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
