CVE-2024-22415: jupyter-lsp is a coding assistance tool for JupyterLab (code navigation + hover suggestions + linters + autocompletion + rename) using Language Server…

PriorityP261critical9.8CVSS 3.1

AVNACLPRNUINSUCHIHAH

EPSS

0.49%

38.5th percentile

jupyter-lsp is a coding assistance tool for JupyterLab (code navigation + hover suggestions + linters + autocompletion + rename) using Language Server Protocol. Installations of jupyter-lsp running in environments without configured file system access control (on the operating system level), and with jupyter-server instances exposed to non-trusted network are vulnerable to unauthorised access and modification of file system beyond the jupyter root directory. This issue has been patched in version 2.2.2 and all users are advised to upgrade. Users unable to upgrade should uninstall jupyter-lsp.

Affected

2 ranges

Vendor	Product	Version range	Fixed in
jupyter-lsp	jupyterlab-lsp	< 2.2.2	2.2.2
jupyter	language_server_protocol_integration	< 2.2.2	2.2.2

Detection & IOCsextracted from sources · hover to see the quote

→CVE-2024-22415 involves unauthorized access and modification of the file system beyond the jupyter root directory in jupyter-lsp; monitor for file access requests that traverse outside the configured Jupyter root directory. ↗
→Jupyter Notebooks exposed to non-trusted networks are a primary attack surface for CVE-2024-22415; monitor for Jupyter server instances accessible from untrusted or public networks. ↗
→Audit Jupyter Notebook deployments for missing OS-level file system access controls, which is the precondition enabling CVE-2024-22415 exploitation. ↗
→Jupyter listens on multiple TCP ports using HMAC-SHA256; monitor shell_port, iopub_port, control_port, and hb_port for unexpected external connections as part of detecting exploitation attempts. ↗

·The vulnerability only applies to jupyter-lsp versions prior to 2.2.2; environments already on 2.2.2+ are patched. ↗
·Exploitation requires two conditions to be simultaneously true: no OS-level file system access control configured AND the jupyter-server exposed to a non-trusted network. Environments with proper OS-level controls are less exposed. ↗
·Jupyter uses encrypted WebSocket datagrams which may limit visibility for network-based detection tools. ↗

Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.