Git LFS permits exfiltration of credentials via crafted HTTP URLs
git-lfs
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/git-lfs/git-lfs Go |
| No fix yet |
| github.com/git-lfs/git-lfs/v3 Go |
|
|
git-lfs
| Product | Affected | Fixed in |
|---|---|---|
| github.com/git-lfs/git-lfs Go |
| No fix yet |
| github.com/git-lfs/git-lfs/v3 Go |
|
|
Git LFS is a Git extension for versioning large files. When Git LFS requests credentials from Git for a remote host, it passes portions of the host's URL to the `git-credential(1)` command without checking for embedded line-ending control characters, and then sends any credentials it receives back from the Git credential helper to the remote host. By inserting URL-encoded control characters such as line feed (LF) or carriage return (CR) characters into the URL, an attacker may be able to retrieve a user's Git credentials. This problem exists in all previous versions and is patched in v3.6.1. All users should upgrade to v3.6.1. There are no workarounds known at this time.
From the CVE record · GitHub_M
Git LFS passes remote-host URLs to git-credential without checking for embedded line-ending control characters. If a user uses an attacker-crafted URL containing encoded LF or CR characters, an attacker may be able to obtain credentials returned by the Git credential helper. Exploitation requires the affected user to use that URL and have credentials returned by the helper.
Users of github.com/git-lfs/git-lfs/v3 versions 3.0.0 through 3.6.0 and the github.com/git-lfs/git-lfs Go package should check their installations.