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.
Release Notes
jupyter-lsp/jupyterlab-lsp (jupyter-lsp)
### [`v2.2.2`](https://togithub.com/jupyter-lsp/jupyterlab-lsp/blob/HEAD/CHANGELOG.md#jupyter-lsp-222)
- bug fixes:
- address warning about renamed `extension_points` ([#1035](https://togithub.com/jupyter-lsp/jupyterlab-lsp/issues/1035))
- fix compatibility with jupyter server 1.x
- fix an authentication-related security vulnerability (see [the advisory](https://togithub.com/jupyter-lsp/jupyterlab-lsp/security/advisories/GHSA-4qhp-652w-c22x) for details)
- enhancements:
- add authorization support (`lsp` resource, jupyter-server v2+ only) - this allows server operators for fine grained access control, e.g. in case if specific users (such as guest or read-only users) should not be allowed to access LSP; this is in addition to authentication fixes
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
==2.2.1->==2.2.2GitHub Vulnerability Alerts
CVE-2024-22415
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.
Release Notes
jupyter-lsp/jupyterlab-lsp (jupyter-lsp)
### [`v2.2.2`](https://togithub.com/jupyter-lsp/jupyterlab-lsp/blob/HEAD/CHANGELOG.md#jupyter-lsp-222) - bug fixes: - address warning about renamed `extension_points` ([#1035](https://togithub.com/jupyter-lsp/jupyterlab-lsp/issues/1035)) - fix compatibility with jupyter server 1.x - fix an authentication-related security vulnerability (see [the advisory](https://togithub.com/jupyter-lsp/jupyterlab-lsp/security/advisories/GHSA-4qhp-652w-c22x) for details) - enhancements: - add authorization support (`lsp` resource, jupyter-server v2+ only) - this allows server operators for fine grained access control, e.g. in case if specific users (such as guest or read-only users) should not be allowed to access LSP; this is in addition to authentication fixesConfiguration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.