Vulnerability in Git-Scm Git
CVE-2022-24975
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.
EPSS: 0.026 (84.0th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
Affected products
- Git-scm Git
- N/a — versions n/a
Weakness classification (CWE)
Public proof-of-concept exploits
References
- cve@mitre.org (Exploit, Third Party Advisory)
- cve@mitre.org (Exploit, Vendor Advisory)
- cve@mitre.org
- cve@mitre.org
Frequently asked questions
- What is CVE-2022-24975?
- CVE-2022-24975 is a high-severity vulnerability in Git-Scm Git, classified under Exposure of Resource to Wrong Sphere. CVSS score: 7.5/10. Published 2022-02-11.
- How severe is CVE-2022-24975?
- High severity. CVSS v3 base score is 7.5 out of 10.
- Is CVE-2022-24975 known to be exploited?
- 6 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.