Bug 2054686 (CVE-2022-24975)

Summary:	CVE-2022-24975 git: The --mirror option for git leaks secret for deleted content, aka the "GitBleed"
Product:	[Other] Security Response	Reporter:	TEJ RATHI <trathi>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	amahdal, bdettelb, besser82, caswilli, chrisw, dhalasz, fjansen, hhorak, johannes, jorton, jwong, kaycoth, micjohns, opohorel, psegedy, pstodulk, sebastian.kisela, sthirugn, tkasparek, tmz, tsasak, vkrizan, vmugicag
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:	A flaw known as "GitBleed" was found in Git, where repositories cloned via the "–mirror" option may leak secrets or sensitive information if not properly removed/deleted earlier. This flaw allows attackers and bug bounty hunters to use this discrepancy in Git behavior to find hidden secrets and other sensitive data in public repositories.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-09 21:15:31 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2054692

Description TEJ RATHI 2022-02-15 14:03:13 UTC

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.

https://wwws.nightwatchcybersecurity.com/2022/02/11/gitbleed/
https://github.com/git/git/blob/2dc94da3744bfbbf145eca587a0f5ff480cc5867/Documentation/git-clone.txt#L185-L191

Comment 2 TEJ RATHI 2022-03-08 07:57:43 UTC

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 fuller copy of their own repositories using the “–mirror” option and remove sensitive data using tools like BFG or git-filter-repo.

Comment 3 Product Security DevOps Team 2022-05-09 21:15:28 UTC

This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2022-24975