On 12-10-2019, Git released patch v2.24.1 to address several common vulnerabilities and exposures, or CVE. For those unfamiliar with what CVE is, it is a dictionary that provides definitions for publicly disclosed cybersecurity vulnerabilities and exposures.

These Security Vulnerabilities are Critical

These security issues could allow complete takeover of a computer through the use of various git commands. They can affect all Git and GitKraken users, especially those that have exposure to lots of obscure public repos.

Recommend Immediate Actions:

1. Update your GitKraken installation to v6.4 or later
2. If you use git on the CLI, update it to v2.24.1

GitKraken utilizes libgit2 for handling its Git operations, but that does not mean it is immune to these vulnerabilities. Fortunately, the libgit2 team has merged in a fix for these new vulnerabilities which are included in GitKraken v6.4.0 and later.

This includes fixes for:

• CVE-2019-1348
• CVE-2019-1349
• CVE-2019-1350
• CVE-2019-1351
• CVE-2019-1352
• CVE-2019-1353
• CVE-2019-1354
• CVE-2019-1387

For users who only use GitKraken, please be sure to always update GitKraken to the latest available version whether that is through our updater or our downloads page. We actively monitor security channels and want to ensure our users are not prone to these vulnerabilities and exposures. 

For any users who utilize Git for the CLI, Git Hooks, or Git LFS, it is advisable to also make sure your current version of Git is v2.24.1 or later. You can download the latest version of Git here.