git2 has potential undefined behavior when dereferencing Buf structGHSA-j39j-6gw9-jw6h
Fix: rust-lang/git2-rs#1213GHSA-j39j-6gw9-jw6h is a security vulnerability in git2. A fix is available for git2 — see the affected versions and patch details below.
Real-World Exposure
git2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
If the Buf struct is dereferenced immediately after calling new() or default() on the Buf struct, a null pointer is passed to the unsafe function slice::from_raw_parts. According to the safety section documentation of the function, data must be non-null and aligned even for zero-length slices or slices of ZSTs. Thus, passing a null pointer will lead to undefined behavior.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | git2 | all versions | 0.20.4cargo update -p git2 --precise 0.20.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for git2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update git2 to 0.20.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j39j-6gw9-jw6h is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-j39j-6gw9-jw6h in your dependencies?
Find it across crates.io, including transitive dependencies.