CVE-2022-24975
Published: 11 February 2022
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.
Notes
| Author | Note |
|---|---|
| eslerm | --mirror appears to work as intended and clearly documents that all refs are copied (which includes deleted branches and git reset data) vendor diputes CVE |
Priority
Status
| Package | Release | Status |
|---|---|---|
|
git Launchpad, Ubuntu, Debian |
bionic |
Ignored
(documentation patch only)
|
| focal |
Ignored
(documentation patch only)
|
|
| impish |
Ignored
(end of life)
|
|
| jammy |
Ignored
(documentation patch only)
|
|
| trusty |
Ignored
(end of standard support)
|
|
| upstream |
Ignored
(documentation patch only)
|
|
| xenial |
Ignored
(documentation patch only)
|
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 7.5 |
| Attack vector | Network |
| Attack complexity | Low |
| Privileges required | None |
| User interaction | None |
| Scope | Unchanged |
| Confidentiality | High |
| Integrity impact | None |
| Availability impact | None |
| Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |