← Back
CVE-2025-30370
OS Command Injection in jupyterlab-git (CVE-2025-30370)
Summary
OS command injection in jupyterlab-git (CVE-2025-30370). Data can be tampered with by attackers. Exploitable via ``pwned.txt``. Mitigation: upgrade to `0.51.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-30370** has been found in jupyterlab-git.
Attackers can target a specific entry point like ``pwned.txt`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: ?/10.
What to do: upgrade jupyterlab-git to **0.51.1** or later.
If unsure, ask your IT team or search "jupyterlab-git CVE-2025-30370" on the vendor's site.
CVE-2025-30370 (jupyterlab-git) — CWE-78 /
Attack vector: local
Attack surface: `pwned.txt` / `cwd`
Patched: `0.51.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.
❓ What is the problem
**OS command injection** (CWE-78) exists in jupyterlab-git. Attackers reach the vulnerable code path via ``pwned.txt`` without authentication.
📍 Affected scope
jupyterlab-git — . Attack surface: `pwned.txt` / `cwd`.
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to **0.51.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'jupyterlab-git' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'jupyterlab-git' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `jupyterlab-git` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade jupyterlab-git to 0.51.1ステージング環境で 0.51.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
jupyterlab-git
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.51.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-30370
- advisory https://github.com/advisories/GHSA-cj5w-8mjf-r5f8
- package https://github.com/jupyterlab/jupyterlab-git
- package https://pypi.org/project/jupyterlab-git
- web https://github.com/jupyterlab/jupyterlab-git/security/advisories/GHSA-cj5w-8mjf-r5f8
- web https://github.com/jupyterlab/jupyterlab-git/pull/1196
- web https://github.com/jupyterlab/jupyterlab-git/commit/b46482993f76d3a546015c6a94ebed8b77fc2376
- web https://github.com/jupyterlab/jupyterlab-git/blob/7eb3b06f0092223bd5494688ec264527bbeb2195/src/commandsAndMenu.tsx#L175-L184