![]() As of this writing, there is no evidence that the weakness has been used to breach accounts in the wild. In a Monday advisory, keypair's maintainer Julian Gruber wrote, "This could enable an attacker to decode confidential messages or gain unauthorised access to a victim's account." Since then, the problem has been fixed in keypair version 1.0.4 and GitKraken version 8.0.1.Īxosoft developer Dan Suceava is credited with uncovering the security flaw, while GitHub security engineer Kevin Jones is credited with determining the bug's cause and position in the source code. However, the flaw resulted in the development of a weaker form of public SSH keys, which, due to their low entropy - a measure of unpredictability - could increase the likelihood of key duplication. GitKraken versions 7.6.x, 7.7.x, and 8.0.0, released between May 12, 2021, and September 27, 2021, have been found to be affected. The problematic dependency, "keypair," is an open-source SSH key creation package that enables users to generate RSA keys for authentication purposes. ![]() We would also like to thank Julian Gruber for working with GitHub Security Lab to quickly address the underlying issue in the keypair library and their collaboration on GHSA-3f99-hvg4-qjwj.įor more information, please visit GitKraken’s blog post at. GitHub would like to thank Axosoft for reaching out to GitHub immediately and informing us of this issue. These results can be filtered to specific user agents to identify potentially vulnerable clients. Īdministrators of GitHub Enterprise Server deployments can review the SSH keys added to their instances by reviewing public_key.create actions in the site admin dashboard audit log. For information on how to review your SSH keys, visit. We recommend that you review SSH keys linked to your GitHub account and rotate any keys that could have been generated using the vulnerable / insecure library. This was not the result of a compromise, data breach, or other data exposure event of GitHub or our systems, but rather an issue with a library commonly used to generate SSH keys for use with GitHub. Users whose keys have been revoked by GitHub are being directly notified. Out of an abundance of caution, we’ve also revoked other potentially weak keys associated with these scenarios and blocked their use. The nature of this vulnerability prevents us from identifying all possible weak SSH keys produced by this library and vulnerable clients that used it. We also investigated the possibility that weakly-generated keys in use on came from other third-party clients and integrators also using this vulnerable library. What helped me resolve the issue was to go to GitKraken preferences. In addition to revoking these keys, we have also implemented protections to prevent vulnerable versions of GitKraken from adding newly-generated weak keys by the older, vulnerable versions of the client in the future. Solved-Gitkraken cannot use local SSH agent-eclipse score:18. Today as of 1700 UTC, we’ve revoked all keys generated by these vulnerable versions of the GitKraken client that were in use on, along with other potentially weak keys created by other clients that may have used the same vulnerable dependency. This issue affected versions 7.6.x, 7.7.x, and 8.0.0 of the GitKraken client, and you can read GitKraken’s disclosure on their blog. An underlying issue with a dependency, called keypair, resulted in the GitKraken client generating weak SSH keys. On September 28, 2021, we received notice from the developer Axosoft regarding a vulnerability in a dependency of their popular git GUI client – GitKraken.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |