Vulnerabilities · 2022 · Git-scm
CVE-2022-24975
Git-scm Git vulnerability
The --mirror documentation for Git through 2.35.1 does not mention the availability of deleted content, aka the "GitBleed" issue. This could present a security risk if information-disclosure auditing processes rely on a clone operation without the --mirror option. Note: This has been disputed by multiple 3rd parties who believe this is an intended feature of the git binary and does not pose a security risk.
Affected products
Git. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Git-scm Git runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/git/git/blob/2dc94da3744bfbbf145eca587a0f5ff480cc5867/Documentation/git-clone.t · Exploit
- wwws.nightwatchcybersecurity.com/2022/02/11/gitbleed/ · Exploit
- lore.kernel.org/git/xmqq4k14qe9g.fsf%40gitster.g/
- www.aquasec.com/blog/undetected-hard-code-secrets-expose-corporations/
- nvd.nist.gov/vuln/detail/CVE-2022-24975
- cve.org/CVERecord?id=CVE-2022-24975
More vulnerabilities in Git-scm products
CVE-2025-48384CVE-2024-32465CVE-2024-32021CVE-2024-32020CVE-2024-32004CVE-2023-29007CVE-2023-25652CVE-2023-23946All 41
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.