Home Hacking News Git Remote Execution Vulnerability Patched in Latest Version

Git Remote Execution Vulnerability Patched in Latest Version

by Harikrishna Mekala

The most widely used version control system Git was suffering from a Remote Code Execution vulnerability that allowed malicious code repositories to execute code on a client’s system when being cloned into a user’s computer. Git Source Control was originally started by Linus Torvalds to manage the development of the Linux Kernel. Git is now used by most software developers worldwide. The Git version control is also used by Microsoft Visual Studio Team Services and Heroku.

The latest iteration of the Git 2.17.1 which was released on May 28th contained fixes for the vulnerabilities for CVE-2018-11233 and CVE-2018-11235 which can lead to the Remote Code Execution on the Server.

“The problem is that when you git clone a repository, there is some important configuration that you don’t get from the server,” Edward Thomson, program manager for Visual Studio Team Services at Microsoft, explained in a blog post. “This includes the contents of the .git/config file, and things like hooks, which are scripts that will be run at certain points within the git workflow. For example, the post-checkout hook will be run anytime git checks files out into the working directory.

The configuration of the git folder is cloned from the remote server which would cause a dangerous vulnerability that a remote server could provide which leads to the execution of the code. Thomson said that “Unfortunately, with this submodule configuration vulnerability, that’s exactly what happens. Since the submodule’s repository is checked in to the parent repository, it’s never actually cloned. The submodule repository can therefore actually have a hook already configured.”

Thomson is currently advising the users to update their Git clients to the latest version. The patch has also been backported for Git version 2.13.7, 2.14.4, 2.15.2 and 2.16.4. At present, the Git hosting servers include GitHub, GitLab, Visual Studio Team Services and Heroku. There is also another vulnerability that allows the attackers to trick the code that sanity-checks paths on NTFS to read random and the pieces of the memory.

Take your time to comment on this article.

You may also like

Latest Hacking News

Privacy Preference Center


The __cfduid cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis.

cookie_notice_accepted and gdpr[allowed_cookies] are used to identify the choices made from the user regarding cookie consent.

For example, if a visitor is in a coffee shop where there may be several infected machines, but the specific visitor's machine is trusted (for example, because they completed a challenge within your Challenge Passage period), the cookie allows Cloudflare to identify that client and not challenge them again. It does not correspond to any user ID in your web application, and does not store any personally identifiable information.

__cfduid, cookie_notice_accepted, gdpr[allowed_cookies]


DoubleClick by Google refers to the DoubleClick Digital Marketing platform which is a separate division within Google. This is Google’s most advanced advertising tools set, which includes five interconnected platform components.

DoubleClick Campaign Manager: the ad-serving platform, called an Ad Server, that delivers ads to your customers and measures all online advertising, even across screens and channels.

DoubleClick Bid Manager – the programmatic bidding platform for bidding on high-quality ad inventory from more than 47 ad marketplaces including Google Display Network.

DoubleClick Ad Exchange: the world’s largest ad marketplace for purchasing display, video, mobile, Search and even Facebook inventory.

DoubleClick Search: is more powerful than AdWords and used for purchasing search ads across Google, Yahoo, and Bing.

DoubleClick Creative Solutions: for designing, delivering and measuring rich media (video) ads, interactive and expandable ads.



The _ga is asssociated with Google Universal Analytics - which is a significant update to Google's more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. By default it is set to expire after 2 years, although this is customisable by website owners.

The _gat global object is used to create and retrieve tracker objects, from which all other methods are invoked. Therefore the methods in this list should be run only off a tracker object created using the _gat global variable. All other methods should be called using the _gaq global object for asynchronous tracking.

_gid works as a user navigates between web pages, they can use the gtag.js tagging library to record information about the page the user has seen (for example, the page's URL) in Google Analytics. The gtag.js tagging library uses HTTP Cookies to "remember" the user's previous interactions with the web pages.

_ga, _gat, _gid