Jupyter Notebook file bypasses sanitization, executes JavaScript
CVE-2018-8768 · GHSA-6cwv-x26c-w2q4 · published 2018-07-12 · updated 2024-09-27
- Severity
- High
- CVSS score
- 7.8
- Chance of exploitation (EPSS)
- 1.0%
- Fixed in
- 5.4.1
In Jupyter Notebook before 5.4.1, a maliciously forged notebook file can bypass sanitization to execute JavaScript in the notebook context. Specifically, invalid HTML is 'fixed' by jQuery after sanitization, making it dangerous.
Upgrade notebook to 5.4.1 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| notebook | PyPI | < 5.4.1 | 5.4.1 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalImproper Input Validation in Jupyter Notebookipython, notebook
- HighJupyterLab: Cross-site scripting (XSS) in JupyterLab via notebook cells pasted from the system clipboardjupyterlab, jupyterlab, notebook
- HighJupyterLab's command linker attributes in HTML enable one-click command execution from untrusted contentjupyterlab, notebook
- HighJupyter Notebook Vulnerable to Authentication Token Theft via CommandLinker XSSjupyterlab, notebook
- HighHTML injection in Jupyter Notebook and JupyterLab leading to DOM Clobberingjupyterlab, jupyterlab, notebook
- HighJupyterLab vulnerable to potential authentication and CSRF tokens leakjupyterlab, jupyterlab, notebook
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.