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

NIST’s role in the global tech race against AI

4 min read - Last year, the United States Secretary of Commerce announced that the National Institute of Standards and Technology (NIST) has been put in charge of launching a new public working group on artificial intelligence (AI) that will build on the success of the NIST AI Risk Management Framework to address this rapidly advancing technology.However, recent budget cuts at NIST, along with a lack of strategy implementation, have called into question the agency’s ability to lead this critical effort. Ultimately, the success…

Researchers develop malicious AI ‘worm’ targeting generative AI systems

2 min read - Researchers have created a new, never-seen-before kind of malware they call the "Morris II" worm, which uses popular AI services to spread itself, infect new systems and steal data. The name references the original Morris computer worm that wreaked havoc on the internet in 1988.The worm demonstrates the potential dangers of AI security threats and creates a new urgency around securing AI models.New worm utilizes adversarial self-replicating promptThe researchers from Cornell Tech, the Israel Institute of Technology and Intuit, used what’s…

Passwords, passkeys and familiarity bias

5 min read - As passkey (passwordless authentication) adoption proceeds, misconceptions abound. There appears to be a widespread impression that passkeys may be more convenient and less secure than passwords. The reality is that they are both more secure and more convenient — possibly a first in cybersecurity.Most of us could be forgiven for not realizing passwordless authentication is more secure than passwords. Thinking back to the first couple of use cases I was exposed to — a phone operating system (OS) and a…

Topic updates

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