cve.bz

CVE-2022-24975 (GitBleed) git-scm git: Exposure of Resource to Wrong Sphere

7.5 highExploit referenceEPSS 2.6%

Known as GitBleed

High (7.5) in git-scm git. EPSS 2.6% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
2.6% (unchanged from 2.6% a week ago; 2.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 86th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-668 Exposure of Resource to Wrong Sphere
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-24975 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-24975?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-24975?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-24975 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
git-scm:gitthrough 2.35.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14gitno fix listedDEBIAN-CVE-2022-24975
Ubuntu22.04:LTS, Pro:16.04:LTS, Pro:18.04:LTS and 1 moregitno fix listedUBUNTU-CVE-2022-24975

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Low.

Red Hat's statement

The "GitBleed" issue can't be fixed, because it requires basic user education and can be fixed only by administrators responsible for individual repositories by analyzing a whole copy of their own repositories using the “–mirror” option and removing sensitive data using tools like BFG or git-filter-repo.

Red Hat's mitigation

Organizations can mitigate this by analyzing a fuller copy of their repositories using the “–mirror” option and removing sensitive data using tools like BFG or git-filter-repo. Garbage collection and pruning in git is also recommended.

Organizations should not analyze regular cloned copies (without the “–mirror” option) since that may provide a false sense of security, and should not rely on methods of removing secrets such as deleting a branch or rewinding history via the “git reset” command.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 7gitNot affected
Red Hat Enterprise Linux 8gitNot affected
Red Hat Enterprise Linux 9gitNot affected
Red Hat Software Collectionsrh-git227-gitNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2022-24975.

References

Check your stackJSON