The git lfs checkout and git lfs pull commands did not check for symbolic
links before writing to files in the working tree, which allowed an attacker
to craft a repository containing symbolic or hard links that caused Git LFS
to write to arbitrary file system locations accessible to the user running
these commands.
Also, when the git lfs checkout and git lfs pull commands were run in a bare
repository, they could write to files visible outside the repository.
The complete fix to this issue, specifically the behaviour of git lfs pull,
requires a newer Git version, 2.42.0 or newer.
As a workaround, support for symlinks in Git may be disabled by setting the
core.symlinks configuration option to false, after which further clones and
fetches will not create symbolic links. However, any symbolic or hard links
in existing repositories will still provide the opportunity for Git LFS to
write to their targets.
For Debian 11 bullseye, this problem has been partially fixed in version
Get the latest Linux and open source security news straight to your inbox.