CVE-2021-21300

malicious repositories can execute remote code while cloning

State
Published
Severity
8.0 High
Published
Mar 9, 2021
Updated
Aug 3, 2024
Reserved
Dec 22, 2020

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
3.18.0 HighCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:NGitHub_M

Weaknesses

  • CWE-59 Improper Link Resolution Before File Access ('Link Following')

Affected Products

ProductVersions
gitgit
  • >= 2.14.2, < 2.17.62.17.6Affected
  • >= 2.18.0, < 2.18.5Affected
  • >= 2.19.0, < 2.19.6Affected
  • >= 2.20.0, < 2.20.5Affected
  • >= 2.21.0, < 2.21.4Affected
  • >= 2.22.0, < 2.22.5Affected
  • >= 2.23.0, < 2.23.4Affected
  • >= 2.24.0, < 2.24.4Affected
  • >= 2.25.0, < 2.25.5Affected
  • >= 2.26.0, < 2.26.3Affected
  • >= 2.27.0, < 2.27.1Affected
  • >= 2.28.0, < 2.28.1Affected
  • >= 2.29.0, < 2.29.3Affected
  • >= 2.30.0, < 2.30.1Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.