CVE-2024-22415: Jupyter-LSP Privilege Escalation Flaw

CVE-2024-22415 Overview

CVE-2024-22415 is a critical Path Traversal vulnerability affecting jupyter-lsp, a coding assistance tool for JupyterLab that provides code navigation, hover suggestions, linters, autocompletion, and rename functionality using the Language Server Protocol. Installations of jupyter-lsp running in environments without configured file system access control at the operating system level, and with jupyter-server instances exposed to non-trusted networks, are vulnerable to unauthorized access and modification of the file system beyond the jupyter root directory.

Critical Impact

This vulnerability allows unauthenticated remote attackers to read and modify files outside the intended jupyter root directory, potentially compromising sensitive system files, configuration data, and enabling further attacks on the underlying infrastructure.

Affected Products

• jupyter-lsp versions prior to 2.2.2
• Jupyter Language Server Protocol Integration for JupyterLab
• Jupyter server instances exposed to untrusted networks without OS-level file system access controls

Discovery Timeline

• 2024-01-18 - CVE CVE-2024-22415 published to NVD
• 2024-11-21 - Last updated in NVD database

Technical Details for CVE-2024-22415

Vulnerability Analysis

This vulnerability is classified as a Path Traversal (CWE-22) and Relative Path Traversal (CWE-23) issue. The jupyter-lsp extension fails to properly validate and sanitize file paths provided through the Language Server Protocol interface, allowing attackers to traverse outside the intended jupyter root directory.

When jupyter-server instances are exposed to untrusted networks and the underlying operating system lacks proper file system access controls, an attacker can exploit this vulnerability to access arbitrary files on the system. The vulnerability enables both reading sensitive files (information disclosure) and modifying files (integrity compromise), which could lead to complete system compromise.

The attack requires no authentication and can be executed remotely over the network, making it particularly dangerous for jupyter-lsp deployments accessible from the internet or untrusted network segments.

Root Cause

The root cause of this vulnerability lies in insufficient path validation within the jupyter-lsp codebase. The Language Server Protocol integration accepts file path parameters that are not properly sanitized to prevent directory traversal sequences (such as ../). Without OS-level file system restrictions in place, the jupyter-lsp process can access files outside the intended jupyter workspace directory, effectively bypassing the logical boundary that should contain file operations.

Attack Vector

The vulnerability is exploitable via network access to a vulnerable jupyter-server instance. An attacker can craft malicious Language Server Protocol requests containing directory traversal sequences to access files outside the jupyter root directory.

The attack does not require user interaction or any authentication, and can be executed with low complexity. Since jupyter-lsp inherits the file system permissions of the jupyter-server process, successful exploitation could allow access to any files readable or writable by that process.

The vulnerability allows attackers to read sensitive configuration files, source code, credentials, and other data stored on the system. Additionally, attackers can modify or create files, potentially enabling code execution, backdoor installation, or denial of service by corrupting critical files.

Detection Methods for CVE-2024-22415

Indicators of Compromise

• Unusual file access patterns in jupyter-server logs showing paths outside the jupyter root directory
• Presence of directory traversal sequences (e.g., ../, ..%2f, %2e%2e/) in Language Server Protocol requests
• Unexpected modifications to system files or configuration files outside the jupyter workspace
• Network traffic to jupyter-server containing suspicious path manipulation attempts

Detection Strategies

• Monitor jupyter-server and jupyter-lsp logs for file access requests containing path traversal patterns
• Implement network intrusion detection rules to identify requests with encoded or plain-text directory traversal sequences targeting jupyter endpoints
• Deploy file integrity monitoring on critical system directories to detect unauthorized modifications
• Use Web Application Firewall (WAF) rules to block requests containing directory traversal patterns

Monitoring Recommendations

• Enable verbose logging for jupyter-server to capture all file access operations
• Implement real-time alerting for any file access attempts outside the designated jupyter root directory
• Monitor system authentication logs for any unusual access patterns following jupyter-lsp requests
• Regularly audit jupyter-lsp access logs and correlate with file system access events

How to Mitigate CVE-2024-22415

Immediate Actions Required

• Upgrade jupyter-lsp to version 2.2.2 or later immediately
• Restrict network access to jupyter-server instances to trusted networks only
• Implement operating system-level file system access controls to limit the jupyter process's access scope
• Review access logs for any signs of exploitation prior to patching
• If unable to upgrade, uninstall jupyter-lsp entirely until patching is possible

Patch Information

The jupyter-lsp maintainers have addressed this vulnerability in version 2.2.2. The fix is available through the GitHub commit. All users are strongly advised to upgrade to version 2.2.2 or later. For more details, refer to the GitHub Security Advisory GHSA-4qhp-652w-c22x.

Workarounds

• Uninstall jupyter-lsp if upgrading is not immediately possible
• Implement network segmentation to ensure jupyter-server instances are not accessible from untrusted networks
• Configure operating system-level access controls (such as AppArmor, SELinux, or file system permissions) to restrict the jupyter process to its intended directory
• Deploy a reverse proxy with path validation rules to filter malicious requests before they reach jupyter-server

# Upgrade jupyter-lsp to patched version
pip install --upgrade jupyter-lsp>=2.2.2

# Alternatively, uninstall if upgrade is not possible
pip uninstall jupyter-lsp

# Verify installed version
pip show jupyter-lsp | grep Version