Remote code execution in dependabot-core branch names when cloning
Published 13 Nov 2020 · Updated 8 Jul 2026
Is your project on an affected dependabot-omnibus?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=0.119.0.beta1 <0.125.1
- Fixed in
- 0.125.1
bundle update --conservative dependabot-omnibus # Gemfile: '>= 0.125.1'- Affected
- >=0.119.0.beta1 <0.125.1
- Fixed in
- 0.125.1
bundle update --conservative dependabot-common # Gemfile: '>= 0.125.1'Details
Impact
Remote code execution vulnerability in dependabot-common and dependabot-go_modules when a source branch name contains malicious injectable bash code.
For example, if Dependabot is configured to use the following source branch name: "/$({curl,127.0.0.1})", Dependabot will make a HTTP request to the following URL: 127.0.0.1 when cloning the source repository.
When Dependabot is configured to clone the source repository during an update, Dependabot runs a shell command to git clone the repository:
git clone --no-tags --no-recurse-submodules --depth=1 --branch=<BRANCH> --single-branch <GITHUB_REPO_URL> repo/contents/path
Dependabot will always clone the source repository for go_modules during the file fetching step and can be configured to clone the repository for other package managers using the FileFetcher class from dependabot-common.
source = Dependabot::Source.new(
provider: "github",
repo: "repo/name",
directory: "/",
branch: "/$({curl,127.0.0.1})",
)
repo_contents_path = "./file/path"
fetcher = Dependabot::FileFetchers.for_package_manager("bundler").
new(source: source, credentials: [],
repo_contents_path: repo_contents_path)
fetcher.clone_repo_contentsPatches
The fix was applied to version 0.125.1: https://github.com/dependabot/dependabot-core/pull/2727
Workarounds
Escape the branch name prior to passing it to the Dependabot::Source class.
For example using shellwords:
require "shellwords"
branch = Shellwords.escape("/$({curl,127.0.0.1})")
source = Dependabot::Source.new(
provider: "github",
repo: "repo/name",
directory: "/",
branch: branch,
)Is GHSA-23f7-99jx-m54r in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected dependabot-omnibus, and gives you the command that fixes it.
References
- Linkgithub.com/dependabot/dependabot-core/security/advisories/GHSA-23f7-99jx-m54r
- Advisorynvd.nist.gov/vuln/detail/CVE-2020-26222
- Linkgithub.com/dependabot/dependabot-core/pull/2727
- Linkgithub.com/dependabot/dependabot-core/commit/e089116abbe284425b976f7920e502b8e83a61b5
- Packagegithub.com/dependabot/dependabot-core
- Linkgithub.com/rubysec/ruby-advisory-db/blob/master/gems/dependabot-common/CVE-2020-26222.yml
- Linkgithub.com/rubysec/ruby-advisory-db/blob/master/gems/dependabot-omnibus/CVE-2020-26222.yml
- Linkrubygems.org/gems/dependabot-common
- Linkrubygems.org/gems/dependabot-omnibus
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.