GHSA-22q8-ghmq-63vf json
libgit2-sys affected by memory corruption, denial of service, and arbitrary code execution in libgit2
published 2y ago modified 2mo ago also RUSTSEC-2024-0013
- cvss
- 8.6
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
The [libgit2](https://github.com/libgit2/libgit2/) project fixed three security issues in the 1.7.2 release. These issues are:
* The `git_revparse_single` function can potentially enter an infinite loop on a well-crafted input, potentially causing a Denial of Service. This function is exposed in the `git2` crate via the [`Repository::revparse_single`](https://docs.rs/git2/latest/git2/struct.Repository.html#method.revparse_single) method. * The `git_index_add` function may cause heap corruption and possibly lead to arbitrary code execution. This function is exposed in the `git2` crate via the [`Index::add`](https://docs.rs/git2/latest/git2/struct.Index.html#method.add) method. * The smart transport negotiation may experience an out-of-bounds read when a remote server did not advertise capabilities.
The `libgit2-sys` crate bundles libgit2, or optionally links to a system libgit2 library. In either case, versions of the libgit2 library less than 1.7.2 are vulnerable. The 0.16.2 release of `libgit2-sys` bundles the fixed version of 1.7.2, and requires a system libgit2 version of at least 1.7.2.
It is recommended that all users upgrade.
Patch / fix
- crates.io libgit2-sys 0.16.2
- github.com/rust-lang/git2-rs@9e57876 commit
- github.com/rust-lang/git2-rs#1017 pull request
- github.com/libgit2/libgit2/releases/tag/v1.7.2 release
Is GHSA-22q8-ghmq-63vf in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L |
| OSV | 3.1 | 8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | libgit2-sys | <0.16.2 >=0.0.0-0, <0.16.2 |
0.16.2 |
References
-
github.com
/rust-lang/git2-rs/pull/1017
web
-
github.com
/rust-lang/git2-rs/commit/9e57876be78924c1e5f3f268bb599e3981fe58bb
web
-
github.com
/rust-lang/git2-rs
package
-
rustsec.org
/advisories/RUSTSEC-2024-0013.html
web, advisory
-
crates.io
/crates/libgit2-sys
package
-
github.com
/libgit2/libgit2/releases/tag/v1.7.2
web
Sources
- GitHub Advisory GHSA-22q8-ghmq-63vf
- OSV RUSTSEC-2024-0013
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.