git2 has potential undefined behavior when dereferencing Buf struct
Priority LOW 38CWE-476Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-476.
Summary
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.
Why it matters now
Fix Fixed git2 (crates.io): 0.20.4
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | git2 (crates.io) | before 0.20.4 | 0.20.4 | Patch available | GHSA-j39j-6gw9-jw6h |
- git2 (crates.io) Vendor— Affected before 0.20.4 Fixed in 0.20.4 Patch available GHSA-j39j-6gw9-jw6h
Remediation
- Fix · GHSA-j39j-6gw9-jw6h git2 (crates.io) Fixed in 0.20.4 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-j39j-6gw9-jw6h
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences