Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2021-21300malicious repositories can execute remote code while cloning

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.

Public exploit

An exploit or proof of concept is public: anyone can try it against an unpatched system. The public collections list a Metasploit module for it.

Show the exploits1

Metasploit modules1 module

Modules, templates and exploits as listed by the Metasploit Framework (BSD-3-Clause), ProjectDiscovery's Nuclei templates (MIT) and the Exploit Database (GPLv2), read once a day. Where the data comes from

Timeline

  1. ID reserved

    By GitHub_M

  2. · 3 months later

    Published

  3. · 3 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2021-21300, by who scored it
Scored byCVSSScoreVector
GitHub_MCNA (assigner)3.1High8.0CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N
NVDNVD · Modified3.1High7.5CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
90.8% · top 0.2% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.0.

Affected products

  • git · git

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

References

References14

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2021-21300 badge
[![CVE-2021-21300](https://cveledger.app/badge/CVE-2021-21300.svg)](https://cveledger.app/cve/CVE-2021-21300)

Record last updated .