Vulnerability in dependabot-omnibus (CVE-2020-26222)
Summary
Vulnerability in dependabot-omnibus (CVE-2020-26222). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.125.1 or later.
Original description
The description as published by the source.
Dependabot is a set of packages for automated dependency management for Ruby, JavaScript, Python, PHP, Elixir, Rust, Java, .NET, Elm and Go. In Dependabot-Core from version 0.119.0.beta1 before version 0.125.1, there is a 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. The fix was applied to version 0.125.1. As a workaround, one can escape the branch name prior to passing it to the Dependabot::Source class.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-26222 has been found in dependabot-omnibus.
Successful exploitation can lead to full system takeover.
What to do: upgrade dependabot-omnibus to 0.125.1 or later.
If unsure, ask your IT team or search "dependabot-omnibus CVE-2020-26222" on the vendor's site.
CVE-2020-26222 (dependabot-omnibus) — CWE-74
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.125.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-74) exists in dependabot-omnibus.
Check the vendor advisory for the affected versions of dependabot-omnibus.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 0.125.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'dependabot-omnibus' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'dependabot-omnibus' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
dependabot-omnibusを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade dependabot-omnibus to 0.125.1ステージング環境で 0.125.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- report github.com
- web github.com
- web github.com
- web rubygems.org
- web rubygems.org