gitoxide does not detect SHA-1 collision attacks
GitoxideLabs gitoxide
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| gix-features crates.io |
|
|
| gix-commitgraph crates.io |
|
|
| gix-index crates.io |
|
|
| gix-object crates.io |
|
|
| gix-odb crates.io |
|
|
| gix-pack crates.io |
|
|
| gitoxide crates.io |
|
|
| gitoxide-core crates.io |
|
|
| gix crates.io |
|
|
| gix-archive crates.io |
|
|
| gix-blame crates.io |
|
|
| gix-config crates.io |
|
|
| gix-diff crates.io |
|
|
| gix-dir crates.io |
|
|
| gix-discover crates.io |
|
|
| gix-filter crates.io |
|
|
| gix-fsck crates.io |
|
|
| gix-merge crates.io |
|
|
| gix-negotiate crates.io |
|
|
| gix-protocol crates.io |
|
|
| gix-ref crates.io |
|
|
| gix-revision crates.io |
|
|
| gix-revwalk crates.io |
|
|
| gix-status crates.io |
|
|
| gix-traverse crates.io |
|
|
| gix-worktree crates.io |
|
|
| gix-worktree-state crates.io |
|
|
Original description
gitoxide is an implementation of git written in Rust. Before 0.42.0, gitoxide uses SHA-1 hash implementations without any collision detection, leaving it vulnerable to hash collision attacks. gitoxide uses the sha1_smol or sha1 crate, both of which implement standard SHA-1 without any mitigations for collision attacks. This means that two distinct Git objects with colliding SHA-1 hashes would break the Git object model and integrity checks when used with gitoxide. This vulnerability is fixed in 0.42.0.
From the CVE record · GitHub_M
References
- github.com/GitoxideLabs/gitoxide/security/advisories/GHSA-2frx-2596-x5r6Exploit
- github.com/GitoxideLabs/gitoxide/commit/f253f02a6658b3b7612a50d56c71f5ae4da4ca21
- github.com/CVEProject/cvelistV5/tree/main/cves/2025/31xxx/CVE-2025-31130.json
- nvd.nist.gov/vuln/detail/CVE-2025-31130
- github.com/GitoxideLabs/gitoxide
- rustsec.org/advisories/RUSTSEC-2025-0021.html
- crates.io/crates/gix-features