A vulnerability in Git could allow an attacker to place malicious, auto-executing code in a sub-module.
Organizations that use Git as a code repository are vulnerable to an attack through submodules and should update their code immediately. The vulnerability, described in CVE-2018-17456, can allow arbitrary code to be executed when a user clones a subdirectory containing malicious code.
The vulnerability - an option-injection attack - is described as quite similar to an earlier vulnerability in a GitHub blog post announcing the issue and its solution. That bug, CVE-2017-1000117, previously had been patched.
The option-injection flaw was reported through the GitHub Bug Bounty program on September 23, with a coordinated disclosure date of October 5.
GitHub Desktop, Atom, the CLI version of Git, and applications that might have embedded Git are all affected by the vulnerability. GitHub Enterprise and GitHub.com are not vulnerable to this flaw, however.
About the Author(s)
You May Also Like
The fuel in the new AI race: Data
April 23, 2024Securing Code in the Age of AI
April 24, 2024Beyond Spam Filters and Firewalls: Preventing Business Email Compromises in the Modern Enterprise
April 30, 2024Key Findings from the State of AppSec Report 2024
May 7, 2024Is AI Identifying Threats to Your Network?
May 14, 2024
Black Hat USA - August 3-8 - Learn More
August 3, 2024Cybersecurity's Hottest New Technologies: What You Need To Know
March 21, 2024