August 14, 2017 By Larry Loeb 2 min read

Researchers recently found that three of the most popular version control systems can be tricked into running arbitrary code.

Joern Schneeweisz, a security researcher for Recurity Labs, discovered vulnerabilities that could enable threat actors to steal source code from the code repository or hijack the machine that runs the repository by copying a source code project via a SSH link. This link can be hidden inside modules of the tool so that no direct user action is required to exploit the fault.

Inside the Git LFS Vulnerability

The first vulnerability, which can be configured by a .lfsconfig file, was found in Git LFS, a tool used on GitHub to clone repository files. If a URL in a submodule contains “ssh://-oProxyCommand=some-command,” instead of obtaining a clone, Git LFS would perform the command on the user’s computer. Calling this URL recursively could execute multiple commands. The payload is triggered when the module is updated.

This vulnerability also showed up in the GitLab implementation and was tracked with CVE-2017-12426. Additionally, Schneeweisz discovered that the parent Git project was open to the flaw as well.

Two Additional Vulnerabilities in Version Control Systems

After being informed of the problem, Git issued a fix. However, it seems that there were other version control systems affected by the same vulnerability, which was buried inside the Git clone operation. Bleeping Computer noted that during the attempt to fix Git LFS, Apache Subversion (SVN) and Mercurial were also found to be open to this kind of attack.

Schneeweisz noted that SVN was impacted most because it follows HTTP 301 redirects to svn+ssh:// URLs. “As a result,” he said, “an innocent-looking HTTP URL can be used to trigger a command execution with a 301 redirect.” That means that SVN doesn’t detect HTTP redirects in its repository cloning operations.

However, the issued fix addressed all the problem areas that have been found thus far in all three tools. Users of these systems should be vigilant about patching systems to avoid exploits.

More from

Government cybersecurity in 2025: Former Principal Deputy National Cyber Director weighs in

4 min read - As 2024 comes to an end, it’s time to look ahead to the state of public cybersecurity in 2025.The good news is this: Cybersecurity will be an ongoing concern for the government regardless of the party in power, as many current cybersecurity initiatives are bipartisan. But what will government cybersecurity look like in 2025?Will the country be better off than they are today? What are the positive signs that could signal a good year for national cybersecurity? And what threats should…

FYSA – Adobe Cold Fusion Path Traversal Vulnerability

2 min read - Summary Adobe has released a security bulletin (APSB24-107) addressing an arbitrary file system read vulnerability in ColdFusion, a web application server. The vulnerability, identified as CVE-2024-53961, can be exploited to read arbitrary files on the system, potentially leading to unauthorized access and data exposure. Threat Topography Threat Type: Arbitrary File System Read Industries Impacted: Technology, Software, and Web Development Geolocation: Global Environment Impact: Web servers running ColdFusion 2021 and 2023 are vulnerable Overview X-Force Incident Command is monitoring the disclosure…

2024 trends: Were they accurate?

4 min read - The new year always kicks off with a flood of prediction articles; then, 12 months later, our newsfeed is filled with wrap-up articles. But we are often left to wonder if experts got it right in January about how the year would unfold. As we close out 2024, let’s take a moment to go back and see if the crystal balls were working about how the year would play out in cybersecurity.Here are five trends that were often predicted for…

Topic updates

Get email updates and stay ahead of the latest threats to the security landscape, thought leadership and research.
Subscribe today