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.
References
Configurations
History
01 Aug 2024, 09:15
Type | Values Removed | Values Added |
---|---|---|
References |
|
02 Jul 2024, 14:15
Type | Values Removed | Values Added |
---|---|---|
References |
|
07 May 2024, 17:15
Type | Values Removed | Values Added |
---|---|---|
Summary | (en) 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. |
Information
Published : 2022-02-11 20:15
Updated : 2024-08-03 05:15
NVD link : CVE-2022-24975
Mitre link : CVE-2022-24975
CVE.ORG link : CVE-2022-24975
JSON object : View
Products Affected
git-scm
- git
CWE
CWE-668
Exposure of Resource to Wrong Sphere