Bug 1117056 - (CVE-2018-19351) VUL-0: CVE-2018-19351: python-jupyter_notebook: XSS via an untrusted notebook
(CVE-2018-19351)
VUL-0: CVE-2018-19351: python-jupyter_notebook: XSS via an untrusted notebook
Status: RESOLVED FIXED
Classification: openSUSE
Product: openSUSE Distribution
Classification: openSUSE
Component: Security
Leap 15.0
Other Other
: P3 - Medium : Normal (vote)
: ---
Assigned To: Security Team bot
Security Team bot
https://smash.suse.de/issue/219431/
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-11-22 14:20 UTC by Robert Frohl
Modified: 2020-01-16 14:53 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Frohl 2018-11-22 14:20:52 UTC
rh#1651973

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.

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1651973
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-19351
http://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-19351.html
http://www.cvedetails.com/cve/CVE-2018-19351/
https://pypi.org/project/notebook/#history
https://groups.google.com/forum/#!topic/jupyter/hWzu2BSsplY
https://github.com/jupyter/notebook/commit/107a89fce5f413fb5728c1c5d2c7788e1fb17491
https://github.com/jupyter/notebook/blob/master/docs/source/changelog.rst
Comment 1 Todd R 2018-12-07 19:39:57 UTC
This is already fixed in Factory/Tumbleweed.  Does it need to be backported to anything?
Comment 2 Tomáš Chvátal 2019-07-11 11:36:31 UTC
This is automated batch bugzilla cleanup.

The openSUSE 42.3 changed to end-of-life (EOL [1]) status. As such
it is no longer maintained, which means that it will not receive any
further security or bug fix updates.
As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
openSUSE (At this moment openSUSE Leap 15.1, 15.0 and Tumbleweed) please
feel free to reopen this bug against that version (!you must update the
"Version" component in the bug fields, do not just reopen please), or
alternatively create a new ticket.

Thank you for reporting this bug and we are sorry it could not be fixed
during the lifetime of the release.

[1] https://en.opensuse.org/Lifetime
Comment 3 Marcus Meissner 2019-07-11 15:54:31 UTC
15.0 is still unfixed
Comment 4 Wolfgang Frisch 2020-01-16 14:53:52 UTC
All fixed.