Vulnerability in jupyterlab (CVE-2021-32797)

Summary

vulnerability in jupyterlab (CVE-2021-32797). Confidential information can be exposed externally. Mitigation: upgrade to `1.2.21, 2.2.10, 2.3.2, 3.0.17, 3.1.4` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2021-32797** has been found in jupyterlab. Confidential information can be exposed externally. CVSS score: ?/10. What to do: upgrade jupyterlab to **1.2.21, 2.2.10, 2.3.2, 3.0.17, 3.1.4** or later. If unsure, ask your IT team or search "jupyterlab CVE-2021-32797" on the vendor's site.

CVE-2021-32797 (jupyterlab) — Attack vector: remote (network-reachable) / unauthenticated Patched: `1.2.21, 2.2.10, 2.3.2, 3.0.17, 3.1.4` — 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

**A vulnerability** (unclassified) exists in jupyterlab.

📍 Affected scope

jupyterlab — .

🔥 Severity

Severity: ?. Confidential information can be exposed externally

🔧 How to fix

Update to **1.2.21, 2.2.10, 2.3.2, 3.0.17, 3.1.4**.

🛡️ 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' .` 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

1
Identify exposure identify
```
grep -r 'jupyterlab' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `jupyterlab` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade jupyterlab to 1.2.21, 2.2.10, 2.3.2, 3.0.17, 3.1.4
```
ステージング環境で 1.2.21, 2.2.10, 2.3.2, 3.0.17, 3.1.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Bitnami jupyterlab

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.2.21"},{"introduced":"2.0.0"},{"fixed":"2.2.10"},{"introduced":"2.3.0"},{"fixed":"2.3.2"},{"introduced":"3.0.0"},{"fixed":"3.0.17"},{"introduced":"3.1.0"},{"fixed":"3.1.4"}]}]

PyPI jupyterlab

[{"repo":"https:\/\/github.com\/jupyterlab\/jupyterlab","type":"GIT","events":[{"introduced":"0"},{"fixed":"504825938c0abfa2fb8ff8d529308830a5ae42ed"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.21"},{"introduced":"2"},{"fixed":"2.2.10"},{"introduced":"2.3"},{"fixed":"2.3.2"},{"introduced":"3"},{"fixed":"3.0.17"},{"introduced":"3.1"},{"fixed":"3.1.4"}]}]

PyPI notebook

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.7.11"},{"introduced":"6.0.0"},{"fixed":"6.4.1"}]}]