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.

Published · last modified .

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.

EPSS exploit prediction

EPSS: 0.026 (85.0th percentile), scored .

Low probability of exploitation in the next 30 days, but still tracked. 85th percentile — 85.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2022-24975: held from 0.026 to 0.026.

EPSS over last 30 days · oldest: 0.026 · newest: 0.026 · change: -0.000

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

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.