SVG:Advisory-SVG-CVE-2021-32798

From EGIWiki
Jump to: navigation, search
Main page Software Security Checklist Issue Handling Advisories Notes On Risk Advisory Template More

Advisory-SVG-CVE-2021-32798



Title:       EGI SVG 'ADVISORY' [TLP:WHITE] UP TO CRITICAL risk Remote Code execution in JupyterLab and Jupyter 
Notebook CVE-2021–32797 and CVE-2021–32798  [EGI-SVG-CVE-2021-32798] 

Date:        2021-08-17
Updated:     2021-09-07 - changed to [TLP:WHITE] and placed on the wiki.


Affected software and risk
==========================

UP TO CRITICAL risk vulnerabilities concerning JupyterLab and Jupyter Notebook

Package : JupyterLab and Jupyter Notebook
CVE ID  : CVE-2021–32797, CVE-2021–32798 

Vulnerabilities have been reported in JupyterLab (CVE-2021-32797 [R 1], [R 2]) and Jupyter Notebook (CVE-2021-32798 [R 3], 
[R 4]) which allow untrusted code in a Notebook to execute on load.  


Actions required/recommended
============================

Sites and VOs are recommended to update to the latest version of JupyterLab or Jupyter Notebook as soon as possible. 
There are no recommended mitigations.

Component installation information
==================================

Please see [R 5], [R 6] 

Mitigation
==========

There is no recommended mitigation. 

Affected software details
=========================

This is fixed for the following versions:--

For Jupyter Notebook:--

Patched in the following versions: 5.7.11, 6.4.1

For JupyterLab

Patched in the following versions: 3.1.4, 3.0.17, 2.3.2, 2.2.10, 1.2.21.

Earlier versions are likely to be vulnerable. 

More information
================

Please see [R 7]. 

The EGI SVG is aware that this is relevant to FedCloud sites and users, but also other sites and VOs. 

More information on Jupyter is available from their website [R 8]

TLP and URL
===========

** WHITE information - Unlimited distribution - see https://wiki.egi.eu/wiki/EGI_CSIRT:TLP for distribution restrictions **  

URL:   https://wiki.egi.eu/wiki/SVG:Advisory-SVG-CVE-2021-32798    

Minor updates may be made without re-distribution by e-mail.

Comments
========

Comments or questions should be sent to svg-rat  at  mailman.egi.eu

If you find or become aware of another vulnerability which is relevant to EGI you may report it by e-mail to  

report-vulnerability at egi.eu
 
the EGI Software Vulnerability Group will take a look according to the procedure defined in [R 9]  

Note that this is undergoing revision to fully handle vulnerabilities in future.


References
==========

[R 1] https://nvd.nist.gov/vuln/detail/CVE-2021-32797

[R 2] https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-32797

[R 3] https://nvd.nist.gov/vuln/detail/CVE-2021-32798

[R 4] https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-32798 

[R 5] https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-4952-p58q-6crx

[R 6] https://github.com/jupyter/notebook/security/advisories/GHSA-hwvq-6gjx-j797 
 
[R 7] https://blog.jupyter.org/cve-2021-32797-and-cve-2021-32798-remote-code-execution-in-jupyterlab-and-jupyter-notebook-a70fae0d3239 

[R 8] https://jupyter.org/

[R 9] https://documents.egi.eu/public/ShowDocument?docid=3145

Credit
======

SVG was alerted to this vulnerability by David Crooks and Baptiste Grenier. 

Timeline  
========
Yyyy-mm-dd  [EGI-SVG-2021-CVE-2021-32798] 

2021-08-13 SVG alerted to this issue by David Crooks and Baptiste Grenier
2021-08-16 Acknowledgement from the EGI SVG to the reporter
2021-08-16 Discussed and agreed it is relevant to FedCloud, other sites and some VOs.
2021-08-16 EGI SVG Risk Assessment completed
2021-08-17 Advisory sent to sites and VOs
2021-09-07 Advisory placed on the wiki


Context
=======

This advisory has been prepared as part of the effort to fulfil EGI SVG's purpose 
"To minimize the risk to the EGI infrastructure arising from software vulnerabilities"

The risk is that assessed by the group, according to the EGI SVG issue handling procedure [R 9]  in the context 
of how the software is used in the EGI infrastructure. It is the opinion of the group, we do not guarantee it to be correct. 
The risk may also be higher or lower in other deployments depending on how the software is used.   

-----------------------------
This advisory is subject to the Creative commons licence https://creativecommons.org/licenses/by/4.0/ and 
the EGI https://www.egi.eu/ Software Vulnerability Group must be credited. 
-----------------------------

Note that the SVG issue handling procedure is currently under review, to take account of the increasing inhomogeneity 
of the EGI infrastructure. 

On behalf of the EGI SVG,