CVE-2020-52609.3CriticalCWE-20

CVE-2020-5260: malicious URLs may cause Git to present stored credentials to the wrong server

git

Vendor fix available · Affected: git · Exploitation: likely to be exploited (10% or more)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

14.9%probability of exploitation in the next 30 days

96th percentile

050100

Higher than 96% of scored CVEs

9.3CriticalCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. Git uses external "credential helper" programs to store and retrieve passwords or other credentials from secure storage provided by the operating system. Specially-crafted URLs that contain an encoded newline can inject unintended values into the credential helper protocol stream, causing the credential helper to retrieve the password for one server (e.g., good.example.com) for an HTTP request being made to another server (e.g., evil.example.com), resulting in credentials for the former being sent to the latter. There are no restrictions on the relationship between the two, meaning that an attacker can craft a URL that will present stored credentials for any host to a host of their choosing. The vulnerability can be triggered by feeding a malicious URL to git clone. However, the affected URLs look rather suspicious; the likely vector would be through systems which automatically clone URLs not visible to the user, such as Git submodules, or package systems built around Git. The problem has been patched in the versions published on April 14th, 2020, going back to v2.17.x. Anyone wishing to backport the change further can do so by applying commit 9a6bbee (the full release includes extra checks for git fsck, but that commit is sufficient to protect clients against the vulnerability). The patched versions are: 2.17.4, 2.18.3, 2.19.4, 2.20.3, 2.21.2, 2.22.3, 2.23.2, 2.24.2, 2.25.3, 2.26.1.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

git · git< 2.17.4; >= 2.18.0, < 2.18.3; >= 2.19.0, 2.19.4; >= 2.20.0, < 2.20.3; >= 2.21.0, < 2.21.2; >= 2.22.0, < 2.22.3 and 4 more

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Input Validation · Input Validation and Logic
Vendor: git
Published: April 2020
Band: Likely to be exploited (10% or more), April 2020

CoverageNo articles yet

No CyberSIXT article names CVE-2020-5260 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

7 more references are in the CVE record.