CVE-2021-32798PYSEC-2021-118BIT-JUPYTER-BASE-NOTEBOOK-2021-32798BIT-JUPYTER-NOTEBOOK-2021-32798GHSA-HWVQ-6GJX-J797
Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) in notebook
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.4.1, 5.7.11
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Jupyter notebook is a web-based notebook environment for interactive computing. In affected versions untrusted notebook can execute code on load. Jupyter Notebook uses a deprecated version of Google Caja to sanitize user inputs. A public Caja bypass can be used to trigger an XSS when a victim opens a malicious ipynb document in Jupyter Notebook. The XSS allows an attacker to execute arbitrary code on the victim computer using Jupyter APIs.
Timeline
- CVE published
- Record last updated
Affected versions
- jupyter notebook
From 6.0.0 · fixed in 6.4.1; fixed in 5.7.11
- notebookPyPI
From 5.7.0 · fixed in 5.7.11
- notebookPyPI
fixed in 5.7.11
- notebookPyPI
From 6.0.0 · fixed in 6.4.1