JupyterLab Desktop: TCC Bypass via Misconfigured Node Fuses
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| jupyterlab | jupyterlab-desktop | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Jupyter | Jupyterlab-desktop |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.206% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Jupyter
Jupyter jupyterlab-desktop |
|
| Vendors & Products |
Jupyter
Jupyter jupyterlab-desktop |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | JupyterLab Desktop is the cross-platform desktop application for JupyterLab. Prior to 4.6.2-1, JupyterLab Desktop for macOS shipped with Electron's RunAsNode fuse enabled, allowing ELECTRON_RUN_AS_NODE to execute arbitrary Node.js code in the application process. An attacker who can already execute code as the current user can therefore run code in JupyterLab Desktop's context and inherit TCC permissions previously granted to the application, including access to protected Documents, Desktop, or Downloads folders without another macOS prompt. Exploitation requires existing local code execution and prior TCC grants; it does not provide initial or remote code execution. Windows and Linux are not affected. This vulnerability is fixed in 4.6.2-1. | |
| Title | JupyterLab Desktop: TCC Bypass via Misconfigured Node Fuses | |
| Weaknesses | CWE-250 CWE-693 CWE-94 |
|
| References |
| |
| Metrics |
cvssV3_1
|