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. It makes it so much easier to look at the file, he says. This is just the cherry on top, reports Kyle Smith, GitKraken Developer at Axosoft. In addition to being able to edit, syntax highlighting is a welcomed addition in both the free and pro versions. For information on how to review your SSH keys, visit. Meet GitKraken, the creator of legendary Git tools for developers and teams - like the GitKraken Client, with Git GUI and CLI, Git Integration for Jira. David Koontz, GitKraken Developer at Axosoft. 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. Meet GitKraken, the creator of legendary Git tools for developers and teams - like the GitKraken Client, with Git GUI and CLI, Git Integration for Jira, and GitLens for VS Code. 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. 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. 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |