Execution with Unnecessary Privileges in JupyterApp
CVE-2022-39286 · GHSA-m678-f26j-3hrp · published 2022-10-26 · updated 2024-09-24
- Severity
- High
- CVSS score
- 8.8
- Chance of exploitation (EPSS)
- 1.5%
- Fixed in
- 4.11.2
- Exploitation No known exploitation
- Automatable No
- Technical impact Total
- CISA SSVC
What kind of vulnerability is it? Who is impacted? We’d like to disclose an arbitrary code execution vulnerability in jupytercore that stems from jupytercore executing untrusted files in the current working directory. This vulnerability allows one user to run code as another.
Upgrade jupyter-core to 4.11.2 or later.
Has the problem been patched? What versions should users upgrade to? Users should upgrade to jupyter_core>=4.11.2.
Is there a way for users to fix or remediate the vulnerability without upgrading? No
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| jupyter-core | PyPI | < 4.11.2 | 4.11.2 |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.