Shulou(Shulou.com)06/01 Report--

Today, I will talk to you about what the remote execution loophole in Git is. Many people may not know much about it. In order to make you understand better, the editor has summarized the following content for you. I hope you can get something according to this article.

According to foreign media BleepingComputer, two days ago, the Git project team announced an arbitrary code execution vulnerability found in the Git command line client, Git Desktop and Atom, which is a serious security vulnerability that may allow malicious warehouses to remotely execute commands on vulnerable computers. According to foreign media reports, two days ago, the Git project team announced an arbitrary code execution vulnerability found in the Git command line client, Git Desktop and Atom, which is a serious security vulnerability that may allow malicious warehouses to remotely execute commands on vulnerable computers.

This vulnerability has been assigned a unique ID of CVE-2018-17456, similar to the previous CVE-2017-1000117 optional injection vulnerability-- a malicious repository can create a new .gitmodules file that contains a URL that begins with a dash.

With dashes, when Git uses the-- recurse-submodules parameter to clone the repository, the command translates URL into an option that can then be used for remote code execution on the computer.

When running "git clone-- recurse-submodules", Git parses the URL field in the .gitmodules file and passes it as a parameter to the "git clone" child process. If the URL field is a string and begins with a dash, the "git clone" subprocess will translate the URL into an option. This could cause users to execute any script in superproject when they run "git clone".

As illustrated by an example, the following vulnerability uses a malicious .gitmodules file (notice how URL starts with a dash) to make Git think this is an option. Then the command "touch VULNERABLE/git@github.com:/timwr/test.git" will be executed.

This vulnerability has been fixed in Git v2.19.1 (with backports in v2.14.5, v2.15.3, v2.16.5, v2.17.2, and v2.18.1), GitHub Desktop 1.4.2, Github Desktop 1.4.3-beta0, Atom 1.31.2 and Atom 1.32.0-beta3.

The Git project team strongly recommends that all users upgrade to the latest version of Git client, Github Desktop or Atom to avoid malicious warehouse attacks.

After reading the above, do you have any further understanding of the remote execution vulnerability in Git? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.