A set of three distinct but related attacks, dubbed 'Clone2Leak,' can leak credentials by exploiting how Git and its credential helpers handle authentication requests. The attack can compromise passwords and access tokens in GitHub Desktop, Git LFS, GitHub CLI/Codespaces, and the Git Credential Manager. The flaws that make 'Clone2Leak' possible were discovered by Japanese researcher RyotaK of GMO Flatt Security, who reported them responsibly to the affected projects. Security updates addressing all flaws have been made available, and impacted users are urged to ensure they're running a safe release to mitigate the risk of having their secrets leaked. Each of the flaws discovered by RyotaK revolves around improper parsing of authentication requests made to credential helpers, allowing an attacker to trick Git into leaking stored credentials to a malicious server. Credential helpers are tools that store and retrieve authentication credentials for when Git interacts with remote repositories, helping avoid repeatedly entering credentials for every Git operation. Attackers can trick Git into leaking stored credentials when a user clones or interacts with a malicious repository. Here is an overview of the three ways the Clone2Leak attack can manifest by exploiting various flaws: All vulnerabilities mentioned above have now been patched, but users should ensure their tools are updated, audit credential configurations, and be cautious when cloning repositories. The safe versions to ...
Clone2Leak attacks exploit Git flaws to steal credentials
BleepingComputer
·Bill Toulas
·Published Jan 27, 2025
·Updated
Affected Software
9 affected components
GitHub Desktop
Git LFS
GitHub CLI
Git Credential Manager
GitHub Desktop
GitHub Git LFS
GitHub CLI
GitHub Codespaces
Git Credential Manager
Frequently Asked Questions
1
What is the main topic of the article?
The article discusses Clone2Leak attacks that exploit vulnerabilities in Git and its credential helpers to steal user credentials.
2
What security implications are discussed in the article?
The article highlights the risk of compromised passwords and access tokens due to the way Git handles authentication.
3
What products or software are affected by the Clone2Leak attacks?
The affected software includes GitHub Desktop, Git LFS, GitHub CLI, and Git Credential Manager.
4
How do the Clone2Leak attacks exploit Git vulnerabilities?
The attacks manipulate the authentication requests processed by Git and its credential helpers.
5
What should users do to protect themselves from Clone2Leak attacks?
Users should be cautious with credential management and ensure their Git software is updated to mitigate these vulnerabilities.