GitLab not affected by Git Security Vulnerabilities CVE-2014-9390

GitLab not affected by Git Security Vulnerabilities CVE-2014-9390

Yesterday, Git reported a serious security vulnerability. This vulnerability affects all official Git Client versions. Due to this vulnerability, git.oschina.net, GitLab.com, GitLab community edition, and Enterprise Edition are not directly affected.

This vulnerability exists when the Git and Git compatible clients access the Git repository, and the file names in the file system are case-insensitive and case-sensitive. Attackers can create a malicious Git tree, causing the local. git/config directory to be directly overwritten when cloning or accessing the resource library. This allows attackers to execute any command on the client machine. Currently, Git clients in OS X and Windows are affected by this vulnerability. Linux is a sensitive file system, so it is not affected.

We strongly recommend that you upgrade the Git client to avoid cloning databases from untrusted sources.

The following Git upgrade version fixes this vulnerability:

• V1.8.5.6, v1.9.5, v2.0.5, v2.1.4, and v2.2.1

• The Git Development Kit libgit2 and JGit also released maintenance versions to fix this problem.

Install GitLab on Ubuntu 12.04

GitLab 5.3 upgrade considerations

Deploy GitLab on CentOS (self-managed Git project repository)

Install GitLab 6.0.2 on RHEL6/CentOS6/ScientificLinux6

CentOS 6.5 GitLab installation tutorial and Related Problems

GitLab details: click here
GitLab: click here

This article permanently updates the link address: