Symlink Attack Affecting git/git package, versions [,2.14.3) [2.17.0,2.17.6) [2.18.0,2.18.5) [2.19.0,2.19.6) [2.20.0,2.20.5) [2.21.0,2.21.4) [2.22.0,2.22.5) [2.23.0,2.23.4) [2.24.0,2.24.4) [2.25.0,2.25.5) [2.26.0,2.26.3) [2.29.0,2.29.3) [2.30.0,2.30.2)
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-UNMANAGED-GITGIT-2372015
- published 26 Jan 2022
- disclosed 9 Mar 2021
- credit Unknown
Introduced: 9 Mar 2021
CVE-2021-21300 Open this link in a new tabHow to fix?
Upgrade git/git
to version 2.14.3, 2.17.6, 2.18.5, 2.19.6, 2.20.5, 2.21.4, 2.22.5, 2.23.4, 2.24.4, 2.25.5, 2.26.3, 2.29.3, 2.30.2 or higher.
Overview
Affected versions of this package are vulnerable to Symlink Attack. 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.