Approved changes feed: RSS · Atom
cpe:2.3:a:jupyter:nbdime:*:*:*:*:*:python:*:*
part: a version: * update: *
| Vendor | Jupyter (3170fc95-7dab-5fb9-942d-251eb444755d) |
|---|---|
| Product | Nbdime (631af4b3-7199-556e-a7b6-594d92e9a80f) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | python |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-41134 |
vulnerable | 2026-06-03 14:45:25.194784 |
Stored XSS in Jupyter nbdime
HIGH (8.7)
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.
Published: 2021-11-03T17:50:10.000Z
Updated: 2024-08-04T02:59:31.698Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.