OS Command Injection in nbgitpuller (CVE-2021-39160)
Summary
OS command injection in nbgitpuller (CVE-2021-39160). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.10.2 or later.
Original description
The description as published by the source.
Impact
Due to an unsanitized input, visiting maliciously crafted links could result in arbitrary code execution in the user environment.
Patches
0.10.2
Workarounds
None, other than upgrade to 0.10.2 or downgrade to 0.8.x.
For more information
If you have any questions or comments about this advisory:
- Open an issue in nbgitpuller
- Email our security team at security@ipython.org
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-2021-39160 has been found in nbgitpuller.
Successful exploitation can lead to full system takeover.
What to do: upgrade nbgitpuller to 0.10.2 or later.
If unsure, ask your IT team or search "nbgitpuller CVE-2021-39160" on the vendor's site.
CVE-2021-39160 (nbgitpuller) — CWE-78
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.10.2 — 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.
OS command injection (CWE-78) exists in nbgitpuller.
Check the vendor advisory for the affected versions of nbgitpuller.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 0.10.2.
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 'nbgitpuller' . 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 'nbgitpuller' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
nbgitpullerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade nbgitpuller to 0.10.2ステージング環境で 0.10.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com