CVE-2024-22415

Description

### Impact 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. ### Patches Version 2.2.2 has been patched. ### Workarounds Users of jupyterlab who do not use jupyterlab-lsp can uninstall jupyter-lsp. ### Credits We would like to credit Bary Levy, researcher of pillar.security research team, for the discovery and responsible disclosure of this vulnerability. Edit: based on advice from pillar.security the Confidentiality/Integrity/Availability were increased to High to reflect potential for critical impact on publicly hosted jupyter-server instances lacking isolation of user privileges on operating system level (for best practices please consult https://jupyterhub.readthedocs.io/en/stable/explanation/websecurity.html#protect-users-from-each-other) and CWE-94 was added due to a potential vulnerability chaining in specific environments.

How to fix CVE-2024-22415

To remediate CVE-2024-22415, upgrade the affected package to a fixed version below.

• —upgrade to 2.2.2 or later

Is CVE-2024-22415 being exploited?

Low — EPSS is 0.2%, meaning exploitation activity has not been observed at scale.

Affected packages (1)

• from 0, < 2.2.2

CVSS scores

References (5)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2024-22415
• PATCHgithub.com/jupyter-lsp/jupyterlab-lsp
• WEBgithub.com/jupyter-lsp/jupyterlab-lsp/commit/4ad12f204ad0b85580fc32137c647baaff044e95
• WEBgithub.com/jupyter-lsp/jupyterlab-lsp/releases/tag/v5.0.2