Jupyter Notebook before 5.7.1 allows XSS via an untrusted notebook because nbconvert responses are considered to have the same origin as the notebook server. In other words, nbconvert endpoints can execute JavaScript with access to the server API. In notebook/nbconvert/handlers.py, NbconvertFileHandler and NbconvertPostHandler do not set a Content Security Policy to prevent this.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2018-19351US | medium6.1 | — | ||
Jupyter Notebook before 5.7.1 allows XSS via an untrusted notebook because nbconvert responses are considered to have the same origin as the notebook server. In other words, nbconv… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/advisories/GHSA-49qr-xh3w-h436ADVISORY
- https://github.com/jupyter/notebook/blob/master/docs/source/changelog.rstWEB
- https://github.com/jupyter/notebook/commit/107a89fce5f413fb5728c1c5d2c7788e1fb17491FIX
- https://groups.google.com/forum/#!topic/jupyter/hWzu2BSsplYWEB
- https://lists.debian.org/debian-lts-announce/2020/11/msg00033.htmlWEB
- https://pypi.org/project/notebook/#historyPACKAGE
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan