What is CVE-2024-22415?

CVE-2024-22415 is a high-severity path traversal vulnerability in jupyter-lsp (pip), affecting versions <= 2.2.1. It is fixed in 2.2.2. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.

How severe is CVE-2024-22415?

CVE-2024-22415 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of jupyter-lsp are affected by CVE-2024-22415?

jupyter-lsp (pip) versions <= 2.2.1 is affected.

Is there a fix for CVE-2024-22415?

Yes. CVE-2024-22415 is fixed in 2.2.2. Upgrade to this version or later.

Is CVE-2024-22415 exploitable, and should I be worried?

Whether CVE-2024-22415 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-22415 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-22415?

Upgrade jupyter-lsp to 2.2.2 or later.

CVE-2024-22415 in jupyter-lsp

Q: How severe is CVE-2024-22415?

CVE-2024-22415 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of jupyter-lsp are affected by CVE-2024-22415?

jupyter-lsp (pip) versions <= 2.2.1 is affected.

Q: Is there a fix for CVE-2024-22415?

Yes. CVE-2024-22415 is fixed in 2.2.2. Upgrade to this version or later.

Q: Is CVE-2024-22415 exploitable, and should I be worried?

Whether CVE-2024-22415 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-22415 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-22415?

Upgrade jupyter-lsp to 2.2.2 or later.

Summary

Unsecured endpoints in the jupyter-lsp server extension

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.

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.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2024-22415 has a CVSS score of 7.3 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.2.2); upgrading removes the vulnerable code path.

Affected versions

jupyter-lsp (<= 2.2.1)

Security releases

jupyter-lsp → 2.2.2 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Version 2.2.2 has been patched.

Frequently Asked Questions

What is CVE-2024-22415? CVE-2024-22415 is a high-severity path traversal vulnerability in jupyter-lsp (pip), affecting versions <= 2.2.1. It is fixed in 2.2.2. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
How severe is CVE-2024-22415? CVE-2024-22415 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of jupyter-lsp are affected by CVE-2024-22415? jupyter-lsp (pip) versions <= 2.2.1 is affected.
Is there a fix for CVE-2024-22415? Yes. CVE-2024-22415 is fixed in 2.2.2. Upgrade to this version or later.
Is CVE-2024-22415 exploitable, and should I be worried? Whether CVE-2024-22415 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-22415 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-22415? Upgrade jupyter-lsp to 2.2.2 or later.