CVE-2021-29417 — gitjacker
CRITICALCVE-2021-29417 is a critical-severity (CVSS 9.8) Path Traversal vulnerability in github.com/liamg/gitjacker. A fix is available for github.com/liamg/gitjacker — see the affected versions and patch details below.
gitjacker arbitrary code execution
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
github.com/liamg/gitjackerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
gitjacker before 0.1.0 allows remote attackers to execute arbitrary code via a crafted .git directory because of directory traversal.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/liamg/gitjacker | all versions | 0.1.0go get github.com/liamg/gitjacker@v0.1.0 |
Affected Products
gitjackergitjacker_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/liamg/gitjacker, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/liamg/gitjacker to 0.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-29417 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2021-29417 in your dependencies?
Find it across Go, including transitive dependencies.