CVE-2021-21300

Git is an open-source distributed revision control system. In affected versions of Git a specially crafted repository that contains symbolic links as well as files using a clean/smudge filter such as Git LFS, may cause just-checked out script to be executed while cloning onto a case-insensitive file system such as NTFS, HFS+ or APFS (i.e. the default file systems on Windows and macOS). Note that clean/smudge filters have to be configured for that. Git for Windows configures Git LFS by default, and is therefore vulnerable. The problem has been patched in the versions published on Tuesday, March 9th, 2021. As a workaound, if symbolic link support is disabled in Git (e.g. via git config --global core.symlinks false), the described attack won't work. Likewise, if no clean/smudge filters such as Git LFS are configured globally (i.e. before cloning), the attack is foiled. As always, it is best to avoid cloning repositories from untrusted sources. The earliest impacted version is 2.14.2. The fix versions are: 2.30.1, 2.29.3, 2.28.1, 2.27.1, 2.26.3, 2.25.5, 2.24.4, 2.23.4, 2.22.5, 2.21.4, 2.20.5, 2.19.6, 2.18.5, 2.17.62.17.6.

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. It outclasses SCM tools like Subversion, CVS, Perforce, and ClearCase with features like cheap local branching, convenient staging areas, and multiple workflows.

Security Fix(es):

Git is an open-source distributed revision control system. In affected versions of Git a specially crafted repository that contains symbolic links as well as files using a clean/smudge filter such as Git LFS, may cause just-checked out script to be executed while cloning onto a case-insensitive file system such as NTFS, HFS+ or APFS (i.e. the default file systems on Windows and macOS). Note that clean/smudge filters have to be configured for that. Git for Windows configures Git LFS by default, and is therefore vulnerable. The problem has been patched in the versions published on Tuesday, March 9th, 2021. As a workaound, if symbolic link support is disabled in Git (e.g. via git config --global core.symlinks False), the described attack won't work. Likewise, if no clean/smudge filters such as Git LFS are configured globally (i.e. before cloning), the attack is foiled. As always, it is best to avoid cloning repositories from untrusted sources. The earliest impacted version is 2.14.2. The fix versions are: 2.30.1, 2.29.3, 2.28.1, 2.27.1, 2.26.3, 2.25.5, 2.24.4, 2.23.4, 2.22.5, 2.21.4, 2.20.5, 2.19.6, 2.18.5, 2.17.62.17.6.(CVE-2021-21300)

Git is an open-source distributed revision control system. In affected versions of Git a specially crafted repository that contains symbolic links as well as files using a clean/smudge filter such as Git LFS, may cause just-checked out script to be executed while cloning onto a case-insensitive file system such as NTFS, HFS+ or APFS (i.e. the default file systems on Windows and macOS). Note that clean/smudge filters have to be configured for that. Git for Windows configures Git LFS by default, and is therefore vulnerable. The problem has been patched in the versions published on Tuesday, March 9th, 2021. As a workaound, if symbolic link support is disabled in Git (e.g. via git config --global core.symlinks false), the described attack won't work. Likewise, if no clean/smudge filters such as Git LFS are configured globally (i.e. before cloning), the attack is foiled. As always, it is best to avoid cloning repositories from untrusted sources. The earliest impacted version is 2.14.2. The fix versions are: 2.30.1, 2.29.3, 2.28.1, 2.27.1, 2.26.3, 2.25.5, 2.24.4, 2.23.4, 2.22.5, 2.21.4, 2.20.5, 2.19.6, 2.18.5, 2.17.62.17.6.

On case-insensitive file systems with support for symbolic links, if Git is configured globally to apply delay-capable clean/smudge filters (such as Git LFS), Git could be fooled into running remote code during a clone (CVE-2021-21300).

This update for git fixes the following issues:

• On case-insensitive filesystems, with support for symbolic links, if Git is configured globally to apply delay-capable clean/smudge filters (such as Git LFS), Git could be fooled into running remote code during a clone. (bsc#1183026, CVE-2021-21300)

This update was imported from the SUSE:SLE-15:Update update project.

This update for git fixes the following issues:

Update from version 2.26.2 to version 2.31.1 (jsc#SLE-18152)

Security fixes:

• CVE-2021-21300: On case-insensitive file systems with support for symbolic links, if Git is configured globally to apply delay-capable clean/smudge filters (such as Git LFS), Git could run remote code during a clone. (bsc#1183026)

Non security changes:

• Add sysusers file to create git-daemon user.
• Remove perl-base and openssh-server dependency on git-coreand provide a perl-Git package. (jsc#SLE-17838)
• fsmonitor bug fixes
• Fix git bisect to take an annotated tag as a good/bad endpoint
• Fix a corner case in git mv on case insensitive systems
• Require only openssh-clients where possible (like Tumbleweed or SUSE Linux Enterprise >= 15 SP3). (bsc#1183580)
• Drop rsync requirement, not necessary anymore.
• Use of pack-redundant command is discouraged and will trigger a warning. The replacement is repack -d.
• The --format=%(trailers) mechanism gets enhanced to make it easier to design output for machine consumption.
• No longer give message to choose between rebase or merge upon pull if the history fast-forwards.
• The configuration variable core.abbrev can be set to no to force no abbreviation regardless of the hash algorithm
• git rev-parse can be explicitly told to give output as absolute or relative path with the --path-format=(absolute|relative) option.
• Bash completion update to make it easier for end-users to add completion for their custom git subcommands.
• git maintenance learned to drive scheduled maintenance on platforms whose native scheduling methods are not 'cron'.
• After expiring a reflog and making a single commit, the reflog for the branch would record a single entry that knows both @{0} and @{1}, but we failed to answer 'what commit were we on?', i.e. @{1}
• git bundle learns --stdin option to read its refs from the standard input.
  Also, it now does not lose refs when they point at the same object.
• git log learned a new --diff-merges=<how> option.
• git ls-files can and does show multiple entries when the index is unmerged, which is a source for confusion unless -s/-u option is in use. A new option --deduplicate has been introduced.
• git worktree list now annotates worktrees as prunable, shows locked and prunable attributes in --porcelain mode, and gained a --verbose option.
• git clone tries to locally check out the branch pointed at by HEAD of the remote repository after it is done, but the protocol did not convey the information necessary to do so when copying an empty repository.
  The protocol v2 learned how to do so.
• There are other ways than .. for a single token to denote a commit range', namely <rev>^! and<rev>^-<n>, but git range-diff` did not understand them.
• The git range-diff command learned --(left|right)-only option to show only one side of the compared range.
• git mergetool feeds three versions (base, local and remote) of a conflicted path unmodified. The command learned to optionally prepare these files with unconflicted parts already resolved.
• The .mailmap is documented to be read only from the root level of a working tree, but a stray file in a bare repository also was read by accident, which has been corrected.
• git maintenance tool learned a new pack-refs maintenance task.
• Improved error message given when a configuration variable that is expected to have a boolean value.
• Signed commits and tags now allow verification of objects, whose two object names (one in SHA-1, the other in SHA-256) are both signed.
• git rev-list command learned --disk-usage option.
• git diff, git log --{skip,rotate}-to=<path> allows the user to discard diff output for early paths or move them to the end of the output.
• git difftool learned --skip-to=<path> option to restart an interrupted session from an arbitrary…

These are all security issues fixed in the git-2.33.0-1.3 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the git-annex-8.20210903-1.2 package on the GA media of openSUSE Tumbleweed.

This update for git fixes the following issues:

• On case-insensitive filesystems, with support for symbolic links, if Git is configured globally to apply delay-capable clean/smudge filters (such as Git LFS), Git could be fooled into running remote code during a clone. (bsc#1183026, CVE-2021-21300)

This update for git fixes the following issues:

• On case-insensitive filesystems, with support for symbolic links, if Git is configured globally to apply delay-capable clean/smudge filters (such as Git LFS), Git could be fooled into running remote code during a clone. (bsc#1183026, CVE-2021-21300)

This update for git fixes the following issues:

Update from version 2.26.2 to version 2.31.1 (jsc#SLE-18152)

Security fixes:

• CVE-2021-21300: On case-insensitive file systems with support for symbolic links, if Git is configured globally to apply delay-capable clean/smudge filters (such as Git LFS), Git could run remote code during a clone. (bsc#1183026)

Non security changes:

• Add sysusers file to create git-daemon user.
• Remove perl-base and openssh-server dependency on git-coreand provide a perl-Git package. (jsc#SLE-17838)
• fsmonitor bug fixes
• Fix git bisect to take an annotated tag as a good/bad endpoint
• Fix a corner case in git mv on case insensitive systems
• Require only openssh-clients where possible (like Tumbleweed or SUSE Linux Enterprise >= 15 SP3). (bsc#1183580)
• Drop rsync requirement, not necessary anymore.
• Use of pack-redundant command is discouraged and will trigger a warning. The replacement is repack -d.
• The --format=%(trailers) mechanism gets enhanced to make it easier to design output for machine consumption.
• No longer give message to choose between rebase or merge upon pull if the history fast-forwards.
• The configuration variable core.abbrev can be set to no to force no abbreviation regardless of the hash algorithm
• git rev-parse can be explicitly told to give output as absolute or relative path with the --path-format=(absolute|relative) option.
• Bash completion update to make it easier for end-users to add completion for their custom git subcommands.
• git maintenance learned to drive scheduled maintenance on platforms whose native scheduling methods are not 'cron'.
• After expiring a reflog and making a single commit, the reflog for the branch would record a single entry that knows both @{0} and @{1}, but we failed to answer 'what commit were we on?', i.e. @{1}
• git bundle learns --stdin option to read its refs from the standard input.
  Also, it now does not lose refs when they point at the same object.
• git log learned a new --diff-merges=<how> option.
• git ls-files can and does show multiple entries when the index is unmerged, which is a source for confusion unless -s/-u option is in use. A new option --deduplicate has been introduced.
• git worktree list now annotates worktrees as prunable, shows locked and prunable attributes in --porcelain mode, and gained a --verbose option.
• git clone tries to locally check out the branch pointed at by HEAD of the remote repository after it is done, but the protocol did not convey the information necessary to do so when copying an empty repository.
  The protocol v2 learned how to do so.
• There are other ways than .. for a single token to denote a commit range', namely <rev>^! and<rev>^-<n>, but git range-diff` did not understand them.
• The git range-diff command learned --(left|right)-only option to show only one side of the compared range.
• git mergetool feeds three versions (base, local and remote) of a conflicted path unmodified. The command learned to optionally prepare these files with unconflicted parts already resolved.
• The .mailmap is documented to be read only from the root level of a working tree, but a stray file in a bare repository also was read by accident, which has been corrected.
• git maintenance tool learned a new pack-refs maintenance task.
• Improved error message given when a configuration variable that is expected to have a boolean value.
• Signed commits and tags now allow verification of objects, whose two object names (one in SHA-1, the other in SHA-256) are both signed.
• git rev-list command learned --disk-usage option.
• git diff, git log --{skip,rotate}-to=<path> allows the user to discard diff output for early paths or move them to the end of the output.
• git difftool learned --skip-to=<path> option to restart an interrupted session from an arbitrary…

Matheus Tavares discovered that Git incorrectly handled delay-capable clean/smudge filters when being used on case-insensitive filesystems. A remote attacker could possibly use this issue to execute arbitrary code.