CVE-2021-21300
HIGHGit 2.14.2-2.30.0 - Remote Code Execution via Symbolic Link and Clean/Smudge Filter Interaction
Title source: llmExploitation Summary
EIP tracks 16 public exploits for CVE-2021-21300.
PoCs published by X1cT34m, Maskhe, the-chivalrousZ, including Metasploit module exploits/multi/http/git_lfs_clone_command_exec.
AI-analyzed exploit summary This exploit leverages a Git vulnerability (CVE-2021-21300) where a malicious repository can execute arbitrary code via a symlink attack on Git hooks during clone operations. The PoC creates a repository with a symlink to `.git/hooks` and a malicious `post-checkout` hook to demonstrate code execution.
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.
Exploits (16)
This exploit leverages a Git vulnerability (CVE-2021-21300) where a malicious repository can execute arbitrary code via a symlink attack on Git hooks during clone operations. The PoC creates a repository with a symlink to `.git/hooks` and a malicious `post-checkout` hook to demonstrate code execution.
The repository lacks any functional exploit code and only contains a vague README instructing users to clone it, with a promise of printing 'PWNED' and a reference to an external source. This is characteristic of a social engineering lure.
Technical analysis of CVE-2021-21300, detailing how arbitrary code execution is achieved via malicious Git hooks on case-insensitive filesystems by exploiting symbolic links.
This script exploits CVE-2021-21300 by creating a malicious Git repository with a symbolic link to .git/hooks, allowing arbitrary command execution during Git operations. The post-checkout hook is abused to execute unauthorized commands.
The repository contains only a README.md file with the CVE identifier and no additional technical details or exploit code. It lacks any meaningful content to classify it as a working PoC, scanner, or writeup.
This repository contains a functional exploit for CVE-2021-21300, a Git vulnerability where symbolic link handling in case-insensitive filesystems (e.g., Windows) can lead to remote command execution. The PoC demonstrates how a malicious repository with a symbolic link pointing to `.git/hooks` can execute arbitrary commands during clone operations.
The exploit leverages a Git vulnerability (CVE-2021-21300) by crafting a malicious repository with a symbolic link to `.git/hooks` and a malicious `post-checkout` hook. When cloned, the hook executes arbitrary code (echoing 'PWNED').
The repository contains only a README.md file with the CVE identifier and no additional technical details or exploit code. It is a placeholder with minimal content.
This repository contains a functional exploit for CVE-2021-21300, a Git vulnerability involving malicious hooks during clone operations. The exploit leverages symbolic link manipulation to execute arbitrary code via a crafted Git repository.
This Metasploit module exploits CVE-2021-21300, a vulnerability in Git clients on case-insensitive file systems. It leverages Git LFS and symbolic links to place a malicious Git hook in the `.git/hooks` directory, achieving remote code execution during repository checkout.
References (14)
Scores
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N