Stored XSS in Jupyter nbdime
- 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 1.1.1, 2.1.1, 3.1.1, 5.0.2, 6.1.2, and 1 more
- 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
nbdime provides tools for diffing and merging of Jupyter Notebooks. In affected versions a stored cross-site scripting (XSS) issue exists within the Jupyter-owned nbdime project. It appears that when reading the file name and path from disk, the extension does not sanitize the string it constructs before returning it to be displayed. The diffNotebookCheckpoint function within nbdime causes this issue. When attempting to display the name of the local notebook (diffNotebookCheckpoint), nbdime appears to simply append .ipynb to the name of the input file. The NbdimeWidget is then created, and the base string is passed through to the request API function. From there, the frontend simply renders the HTML tag and anything along with it. Users are advised to patch to the most recent version of the affected product.
Timeline
- CVE published
- Record last updated
Affected versions
- jupyter nbdime
< 1.1.1 - nbdime (pip), < 5.0.2 - nbdime (npm), < 1.0.1 - nbdime-jupyterlab (npm)
- nbdimePyPI
fixed in 1.1.1
- nbdimePyPI
From 2.0.0 · fixed in 2.1.1
- nbdimePyPI
From 3.0.0 · fixed in 3.1.1
- nbdimenpm
fixed in 5.0.2
- nbdimenpm
From 6.0.0 · fixed in 6.1.2
- nbdime-jupyterlabnpm
fixed in 1.0.1
- nbdime-jupyterlabnpm
From 2.0.0 · fixed in 2.1.1
- nbdimePyPI
fixed in 1.1.1; From 2.0.0 · fixed in 2.1.1; From 3.0.0 · fixed in 3.1.1