← Back
CVE-2024-22415
Path Traversal in jupyter-lsp (CVE-2024-22415)
Summary
path traversal in jupyter-lsp (CVE-2024-22415). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.2.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-22415** has been found in jupyter-lsp.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade jupyter-lsp to **2.2.2** or later.
If unsure, ask your IT team or search "jupyter-lsp CVE-2024-22415" on the vendor's site.
CVE-2024-22415 (jupyter-lsp) — CWE-22 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `2.2.2` — apply immediately
Workaround: Users of jupyterlab who do not use jupyterlab-lsp can uninstall jupyter-lsp.
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
**Path traversal** (CWE-22) exists in jupyter-lsp.
📍 Affected scope
jupyter-lsp — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.2.2**.
🛡️ Workaround
Workaround: Users of jupyterlab who do not use jupyterlab-lsp can uninstall jupyter-lsp.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'jupyter-lsp' .` 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 'jupyter-lsp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `jupyter-lsp` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Users of jupyterlab who do not use jupyterlab-lsp can uninstall jupyter-lsp.パッチが適用されるまでの応急処置として、Users of jupyterlab who do not use jupyterlab-lsp can uninstall jupyter-lsp. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade jupyter-lsp to 2.2.2ステージング環境で 2.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
jupyter-lsp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-22415
- advisory https://github.com/advisories/GHSA-4qhp-652w-c22x
- package https://github.com/jupyter-lsp/jupyterlab-lsp
- package https://pypi.org/project/jupyter-lsp
- web https://github.com/jupyter-lsp/jupyterlab-lsp/security/advisories/GHSA-4qhp-652w-c22x
- web https://github.com/jupyter-lsp/jupyterlab-lsp/commit/4ad12f204ad0b85580fc32137c647baaff044e95
- web https://github.com/jupyter-lsp/jupyterlab-lsp/releases/tag/v5.0.2