# CVE-2022-24975: Information disclosure in n/a

> Git's documentation fails to warn that standard clones may expose deleted content, potentially leading to unintended information disclosure during audits.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-24975, GHSA-wx8f-p63x-543f, ROOT-OS-DEBIAN-12-CVE-2022-24975, UBUNTU-CVE-2022-24975

## What is CVE-2022-24975?

CVE-2022-24975 is a high-severity vulnerability in n/a, published on 11 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2022-24975?

It affects 1 product.


Products: Git-Scm Git.

## How do I fix CVE-2022-24975?

No fix published yet.

## Is CVE-2022-24975 being exploited?

There is no known exploitation of CVE-2022-24975 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-23521](https://insights.sbomify.com/CVE-2022-23521/): gitattributes parsing integer overflow in git (critical 9.8)
- [CVE-2022-41903](https://insights.sbomify.com/CVE-2022-41903/): Integer overflow in `git archive`, `git log --format` leading to RCE in git (critical 9.8)
- [CVE-2019-1353](https://insights.sbomify.com/CVE-2019-1353/): Security feature bypass in Git (critical 9.8)
- [CVE-2016-2315](https://insights.sbomify.com/CVE-2016-2315/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-2324](https://insights.sbomify.com/CVE-2016-2324/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24975 and fix it if it is affected.

What it is: CVE-2022-24975 is a high-severity vulnerability in n/a, published on 11 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-24975 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-24975/ (Markdown: https://insights.sbomify.com/CVE-2022-24975/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24975
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24975
- OSV: https://osv.dev/vulnerability/CVE-2022-24975

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-24975/
Summaries are generated and may contain mistakes; the official description above is the record.