ubuntu-cve-2025-31130
Vulnerability from osv_ubuntu
Published
2025-04-04 15:15
Modified
2026-05-20 15:17
Summary
Details
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.
Severity
6.8 (Medium)
N/A (UNKNOWN)
References
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "librust-gix-features-dev",
"binary_version": "0.36.1-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "rust-gix-features",
"purl": "pkg:deb/ubuntu/rust-gix-features@0.36.1-1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.36.0-1",
"0.36.0-2",
"0.36.1-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "librust-gix-features-dev",
"binary_version": "0.39.1-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "rust-gix-features",
"purl": "pkg:deb/ubuntu/rust-gix-features@0.39.1-2?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.39.1-1",
"0.39.1-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "librust-gix-features-dev",
"binary_version": "0.43.1-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "rust-gix-features",
"purl": "pkg:deb/ubuntu/rust-gix-features@0.43.1-1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.39.1-2",
"0.43.1-1"
]
}
],
"aliases": [],
"details": "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.",
"id": "UBUNTU-CVE-2025-31130",
"modified": "2026-05-20T15:17:32Z",
"published": "2025-04-04T15:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2025-31130"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-31130"
},
{
"type": "REPORT",
"url": "https://rustsec.org/advisories/RUSTSEC-2025-0021.html"
},
{
"type": "REPORT",
"url": "https://github.com/GitoxideLabs/gitoxide/security/advisories/GHSA-2frx-2596-x5r6"
},
{
"type": "REPORT",
"url": "https://github.com/GitoxideLabs/gitoxide/commit/4660f7a6f71873311f68f170b0f1f6659a02829d"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2025-31130"
]
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…