GHSA-m4ch-rfv5-x5g3 is a medium-severity (CVSS 6.8) CWE-347 vulnerability in libgit2-sys. A fix is available for libgit2-sys — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-m4ch-rfv5-x5g3.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
libgit2-sys🦀libgit2-sys🦀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
The git2 and libgit2-sys crates are Rust wrappers around the libgit2 C library. It was discovered that libgit2 1.5.0 and below did not verify SSH host keys when establishing an SSH connection, exposing users of the library to Man-In-the-Middle attacks.
The libgit2 team assigned CVE-2023-22742 to this vulnerability. The following versions of the libgit2-sys Rust crate have been released:
- libgit2-sys 0.14.2, updating the underlying libgit2 C library to version 1.5.1.
- libgit2-sys 0.13.5, updating the underlying libgit2 C library to version 1.4.5.
A new git2 crate version has also been released, 0.16.1. This version only bumps its libgit2-sys dependency to ensure no vulnerable libgit2-sys versions are used, but contains no code changes: if you update the libgit2-sys version there is no need to also update the git2 crate version.
You can learn more about this vulnerability in libgit2's advisory
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | libgit2-sys | ≥ 0.14.0&&< 0.14.2 | 0.14.2cargo update -p libgit2-sys --precise 0.14.2 |
| 🦀crates.io | libgit2-sys | all versions | 0.13.5cargo update -p libgit2-sys --precise 0.13.5 |
| 🦀crates.io | git2 | all versions | 0.16.1cargo update -p git2 --precise 0.16.1 |
Affected Products
libgit2libgit2Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libgit2-sys, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update libgit2-sys to 0.14.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m4ch-rfv5-x5g3 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.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Upgrade the package as soon as possible. Users unable to upgrade should ensure that all relevant certificates are manually checked.Source: Red Hat security advisory for GHSA-m4ch-rfv5-x5g3 (CC BY 4.0)
Frequently Asked Questions
Is GHSA-m4ch-rfv5-x5g3 in your dependencies?
Find it across crates.io, including transitive dependencies.