CVSS: 7.5EPSS: 0%CPEs: 2EXPL: 1CVE-2021-32862 – nbconvert vulnerable to cross-site scripting (XSS) via multiple exploit paths
https://notcve.org/view.php?id=CVE-2021-32862
The GitHub Security Lab discovered sixteen ways to exploit a cross-site scripting vulnerability in nbconvert. When using nbconvert to generate an HTML version of a user-controllable notebook, it is possible to inject arbitrary HTML which may lead to cross-site scripting (XSS) vulnerabilities if these HTML notebooks are served by a web server (eg: nbviewer). GitHub Security Lab detectó dieciséis formas de explotar una vulnerabilidad de tipo cross-site scripting en nbconvert. Cuando es usado nbconvert para generar una versión HTML de un cuaderno controlable por el usuario, es posible inyectar HTML arbitrario que puede conllevar a vulnerabilidades de tipo cross-site scripting (XSS) si estos cuadernos HTML son servidos por un servidor web (por ejemplo: nbviewer). • https://github.com/jupyter/nbconvert/security/advisories/GHSA-9jmq-rx5f-8jwq https://github.com/jupyter/nbviewer/security/advisories/GHSA-h274-fcvj-h2wm https://lists.debian.org/debian-lts-announce/2023/06/msg00003.html • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •
CVSS: 9.0EPSS: 0%CPEs: 1EXPL: 0CVE-2022-29241 – Known or guessable hidden files may be accessed in Jupyter Server
https://notcve.org/view.php?id=CVE-2022-29241
Jupyter Server provides the backend (i.e. the core services, APIs, and REST endpoints) for Jupyter web applications like Jupyter Notebook. Prior to version 1.17.1, if notebook server is started with a value of `root_dir` that contains the starting user's home directory, then the underlying REST API can be used to leak the access token assigned at start time by guessing/brute forcing the PID of the jupyter server. While this requires an authenticated user session, this URL can be used from a cross-site scripting payload or from a hooked or otherwise compromised browser to leak this access token to a malicious third party. This token can be used along with the REST API to interact with Jupyter services/notebooks such as modifying or overwriting critical files, such as .bashrc or .ssh/authorized_keys, allowing a malicious user to read potentially sensitive data and possibly gain control of the impacted system. This issue is patched in version 1.17.1. • https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-q874-g24w-4q9g • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVSS: 4.3EPSS: 0%CPEs: 1EXPL: 0CVE-2022-29238 – Forced Browsing in Jupyter Notebook
https://notcve.org/view.php?id=CVE-2022-29238
Jupyter Notebook is a web-based notebook environment for interactive computing. Prior to version 6.4.12, authenticated requests to the notebook server with `ContentsManager.allow_hidden = False` only prevented listing the contents of hidden directories, not accessing individual hidden files or files in hidden directories (i.e. hidden files were 'hidden' but not 'inaccessible'). This could lead to notebook configurations allowing authenticated access to files that may reasonably be expected to be disallowed. Because fully authenticated requests are required, this is of relatively low impact. But if a server's root directory contains sensitive files whose only protection from the server is being hidden (e.g. `~/.ssh` while serving $HOME), then any authenticated requests could access files if their names are guessable. • https://github.com/jupyter/notebook/security/advisories/GHSA-v7vq-3x77-87vg • CWE-425: Direct Request ('Forced Browsing') •
CVSS: 6.5EPSS: 0%CPEs: 1EXPL: 0CVE-2022-31027 – Authorization Bypass Through User-Controlled Key when using CILogonOAuthenticator in oauthenticator
https://notcve.org/view.php?id=CVE-2022-31027
OAuthenticator is an OAuth token library for the JupyerHub login handler. CILogonOAuthenticator is provided by the OAuthenticator package, and lets users log in to a JupyterHub via CILogon. This is primarily used to restrict a JupyterHub only to users of a given institute. The allowed_idps configuration trait of CILogonOAuthenticator is documented to be a list of domains that indicate the institutions whose users are authorized to access this JupyterHub. This authorization is validated by ensuring that the *email* field provided to us by CILogon has a *domain* that matches one of the domains listed in `allowed_idps`.If `allowed_idps` contains `berkeley.edu`, you might expect only users with valid current credentials provided by University of California, Berkeley to be able to access the JupyterHub. • https://github.com/jupyterhub/oauthenticator/security/advisories/GHSA-r7v4-jwx9-wx43 • CWE-639: Authorization Bypass Through User-Controlled Key •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2022-24758 – Insertion of Sensitive Information into Log File affects Jupyter Notebook
https://notcve.org/view.php?id=CVE-2022-24758
The Jupyter notebook is a web-based notebook environment for interactive computing. Prior to version 6.4.9, unauthorized actors can access sensitive information from server logs. Anytime a 5xx error is triggered, the auth cookie and other header values are recorded in Jupyter server logs by default. Considering these logs do not require root access, an attacker can monitor these logs, steal sensitive auth/cookie information, and gain access to the Jupyter server. Jupyter notebook version 6.4.x contains a patch for this issue. • https://github.com/jupyter/notebook/security/advisories/GHSA-m87f-39q9-6f55 • CWE-532: Insertion of Sensitive Information into Log File •