jupyterhub@1.2.0 vulnerabilities
JupyterHub: A multi-user server for Jupyter notebooks
-
latest version
5.2.1
-
latest non vulnerable version
-
first published
10 years ago
-
latest version published
a month ago
-
licenses detected
- [0.1.0,5.0.0b1)
Direct Vulnerabilities
Known vulnerabilities in the jupyterhub package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.Vulnerability | Vulnerable Version |
---|---|
jupyterhub is a JupyterHub: A multi-user server for Jupyter notebooks Affected versions of this package are vulnerable to Improper Privilege Management in How to fix Improper Privilege Management? Upgrade |
[,4.1.6)
[5.0.0b1,5.1.0)
|
jupyterhub is a JupyterHub: A multi-user server for Jupyter notebooks Affected versions of this package are vulnerable to Cross-site Request Forgery (CSRF) due to the mishandling of user input on a malicious subdomain. An attacker can achieve unauthorized access and control over a user's session and potentially gain full access to the JupyterHub API and the user's single-user server by tricking a user into visiting a malicious subdomain. Note: This is only exploitable in single-origin JupyterHub deployments and deployments where user-controlled applications run on subdomains or peer subdomains of either the Hub or a single-user server. How to fix Cross-site Request Forgery (CSRF)? Upgrade |
[,4.1.0)
|
jupyterhub is a JupyterHub: A multi-user server for Jupyter notebooks Affected versions of this package are vulnerable to Information Exposure. Users who have multiple JupyterLab tabs open in the same browser session, may see incomplete logout from the single-user server, as fresh credentials (for the single-user server only, not the Hub) are reinstated after logout if another active JupyterLab session is open while the logout takes place. How to fix Information Exposure? Upgrade |
[,1.5.0)
|