CVE-2021-21300
8.0 · HIGHOverview
CVE-2021-21300 is a high-severity vulnerability affecting git-scm git. It was published on March 9, 2021 and has a CVSS 3.1 base score of 8.0 (HIGH).
This vulnerability has a CVSS 3.1 base score of 8.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
Technical 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.
Remediation
Check the references section for vendor advisories and patches from git-scm. Update git to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| git-scm | git | 0 | Affected |
| apple | xcode | >= 0, < 12.5 | Affected |
| apple | macos | 11.0 | Affected |
References
Frequently Asked Questions
What is CVE-2021-21300?
CVE-2021-21300 is a high-severity vulnerability affecting git-scm git. It was published on March 9, 2021 and has a CVSS 3.1 base score of 8.0 (HIGH).
How severe is CVE-2021-21300?
This vulnerability has a CVSS 3.1 base score of 8.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
How do I fix or remediate CVE-2021-21300?
Check the references section for vendor advisories and patches from git-scm. Update git to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2021-21300?
CyberStrike's AI-powered security agents can automatically detect CVE-2021-21300 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related HIGH CVEs from 2021
View all →systeminformation is an open source system and OS information library for node.js. A command injecti
An Improper Access Control Privilege Escalation Vulnerability was discovered in the User Setting of
An SQL injection Privilege Escalation Vulnerability was discovered in the Orion Platform reported by
Insecure deserialization leading to Remote Code Execution was detected in the Orion Platform version
Insecure Deserialization of untrusted data remote code execution vulnerability was discovered in Pat
Deserialization of Untrusted Data in the Web Console Chart Endpoint can lead to remote code executio
Insecure Deseralization of untrusted data remote code execution vulnerability was discovered in Patc
SAP Web Dispatcher versions - 7.49, 7.53, 7.77, 7.81, KRNL64NUC - 7.22, 7.22EXT, 7.49, KRNL64UC -7.2
uploader.php in the KCFinder integration project through 2018-06-01 for Drupal mishandles validation
An issue was discovered in the PageLayer plugin before 1.1.2 for WordPress. The pagelayer_settings_p
MK-AUTH through 19.01 K4.9 allows CSRF for password changes via the central/executar_central.php?aca
IBM Cloud Pak System 2.3 is vulnerable to cross-site request forgery which could allow an attacker t