CVE-2022-1440 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in git-interface. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for git-interface — see the affected versions and patch details below.
Command Injection vulnerability in [email protected] in yarkeev/git-interface
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
git-interfacenpmDescription
A command injection vulnerability exists in git-interface in the GitHub repository yarkeev/git-interface prior to 2.1.2. If both the git remote and destination directory are provided by user input, then the use of an --upload-pack command-line argument feature of git is also supported for git clone, which would then allow for any operating system command to be spawned by the attacker.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | git-interface | all versions | 2.1.2npm install git-interface@2.1.2 |
Affected Products
git-interfacegit-interface_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for git-interface, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update git-interface to 2.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-1440 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2022-1440 in your dependencies?
Find it across npm, including transitive dependencies.