Application Security

5/31/2018
12:10 PM
Connect Directly
Twitter
Twitter
RSS
E-Mail
50%
50%

Git Fixes Serious Code Repository Vulnerability

GitHub, Visual Studio Team Services, and other code repositories patching to prevent attackers from targeting developer systems.

The team at Git and a range of code repository hosting services that depend upon the Git platform scrambled this week to push out an important security update in the Git ecosystem.

The fix was for a serious vulnerability that would allow attackers to create malicious Git repositories and use them to carry out arbitrary code execution on user's machines. As one of the most popular tools in the modern developer's toolchain, Git powers a number of code repo services, including GitHub, Microsoft Visual Studio Team Services (VSTS), and JGit. 

As such, this flaw threatens machines at the heart of the sensitive developer environment. Developers are strongly urged to update their client software with Git 2.17.1. This update is designed to fix the flaw, which is essentially a vulnerability in the way Git configures submodule repository configuration during cloning - a frequent activity in this day and age of Agile, assembly-line development patterns.

In order to ensure developers are putting this security update in place, Git has built in server-side safeguards to mandate sound hygiene from its user base. Part of the rollout includes updates to Git and Git-based hosting services that block users from uploading suspect submodules. 

"Git will now refuse to work with repositories that contain a submodule configuration like this," said Edward Thomson, program manager for VSTS in an explainer piece to customers on this latest issue. "And Visual Studio Team Services — along with most other hosting providers — will actively reject you from pushing repositories that contain such a submodule configuration, to help protect clients that haven’t yet upgraded."

The efforts to push this update out offers another success story for GitHub's maturing bug bounty program. Git credits Etienne Stalmans for reporting the issue through the bounty program, which has now entered its fifth year in existence. In an update on its bug bounty progress earlier this spring, GitHub reported that in the last year it has doubled its bug bounty payouts and has seen a significant uptick in the number of valid reports received through the program.  

This is good news for an organization that has seen a meteoric growth in its relevance within the enterprise developer community. According to its annual statistics update, GitHub reported that 24 million developers are now using GitHub to host 67 million total code repositories. Among that userbase, 52% of the Fortune 50 and 45% of the Fortune 100 now use GitHub Enterprise.

These usage statistics are a testament to the power and convenience of GitHub, but like any powerfully convenient cloud tool it can come with its security downsides. The developers with Git and GitHub have worked hard to secure the platform itself; this latest update offers evidence of this vigilance. However, GitHub can't always save users from themselves and a lot of the security problems around GitHub have to do with the way users leverage the platform. 

Take the high-profile Uber breach of 57 million users' data. Hackers were able to steal that data from the company's GitHub repository because the company was not using multifactor authentication to protect its account and it was storing user login credentials in plaintext within its code repo. These are remarkably prevalent mistakes, as are other problems like embedding private AWS keys within stored code, which can seriously increase the blast radius of breach events. 

Related Content:

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Worst Password Blunders of 2018 Hit Organizations East and West
Curtis Franklin Jr., Senior Editor at Dark Reading,  12/12/2018
8 Security Tips to Gift Your Loved Ones For the Holidays
Steve Zurier, Freelance Writer,  12/18/2018
How to Engage Your Cyber Enemies
Guy Nizan, CEO at Intsights Cyber Intelligence,  12/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security 2018
This Dark Reading Tech Digest explores the biggest news stories of 2018 that shaped the cybersecurity landscape.
Flash Poll
[Sponsored Content] The State of Encryption and How to Improve It
[Sponsored Content] The State of Encryption and How to Improve It
Encryption and access controls are considered to be the ultimate safeguards to ensure the security and confidentiality of data, which is why they're mandated in so many compliance and regulatory standards. While the cybersecurity market boasts a wide variety of encryption technologies, many data breaches reveal that sensitive and personal data has often been left unencrypted and, therefore, vulnerable.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-16883
PUBLISHED: 2018-12-19
sssd versions from 1.13.0 to before 2.0.0 did not properly restrict access to the infopipe according to the "allowed_uids" configuration parameter. If sensitive information were stored in the user directory, this could be inadvertently disclosed to local attackers.
CVE-2018-17192
PUBLISHED: 2018-12-19
The X-Frame-Options headers were applied inconsistently on some HTTP responses, resulting in duplicate or missing security headers. Some browsers would interpret these results incorrectly, allowing clickjacking attacks. Mitigation: The fix to consistently apply the security headers was applied on th...
CVE-2018-17193
PUBLISHED: 2018-12-19
The message-page.jsp error page used the value of the HTTP request header X-ProxyContextPath without sanitization, resulting in a reflected XSS attack. Mitigation: The fix to correctly parse and sanitize the request attribute value was applied on the Apache NiFi 1.8.0 release. Users running a prior ...
CVE-2018-17194
PUBLISHED: 2018-12-19
When a client request to a cluster node was replicated to other nodes in the cluster for verification, the Content-Length was forwarded. On a DELETE request, the body was ignored, but if the initial request had a Content-Length value other than 0, the receiving nodes would wait for the body and even...
CVE-2018-17195
PUBLISHED: 2018-12-19
The template upload API endpoint accepted requests from different domain when sent in conjunction with ARP spoofing + man in the middle (MiTM) attack, resulting in a CSRF attack. The required attack vector is complex, requiring a scenario with client certificate authentication, same subnet access, a...