https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 08:37:02 +0000 https://cve.radiocsirt.org/vuln/cve-2024-28233 <p><strong>Affected:</strong> jupyterhub</p> <p>JupyterHub is an open source multi-user server for Jupyter notebooks. By tricking a user into visiting a malicious subdomain, the attacker can achieve an XSS directly affecting the former&#39;s session. More precisely, in the context of JupyterHub, this XSS could achieve full access to JupyterHub API and user&#39;s single-user server. The affected configurations are single-origin JupyterHub deployments and JupyterHub deployments with user-controlled applications running on subdomains or peer subdomains of either the Hub or a single-user server. This vulnerability is fixed in 4.1.0.</p> <p><strong>Affected:</strong> jupyterhub</p> <p>JupyterHub is an open source multi-user server for Jupyter notebooks. By tricking a user into visiting a malicious subdomain, the attacker can achieve an XSS directly affecting the former&#39;s session. More precisely, in the context of JupyterHub, this XSS could achieve full access to JupyterHub API and user&#39;s single-user server. The affected configurations are single-origin JupyterHub deployments and JupyterHub deployments with user-controlled applications running on subdomains or peer subdomains of either the Hub or a single-user server. This vulnerability is fixed in 4.1.0.</p> https://cve.radiocsirt.org/vuln/cve-2024-28233 https://cve.radiocsirt.org/vuln/ghsa-7r3h-4ph8-w38g <p><strong>Affected:</strong> PyPI: jupyterhub</p> <p>### Impact</p> <p>Affected configurations:</p> <p>- Single-origin JupyterHub deployments - JupyterHub deployments with user-controlled applications running on subdomains or peer subdomains of either the Hub or a single-user server.</p> <p>By tricking a user into visiting a malicious subdomain, the attacker can achieve an XSS directly affecting the former&#39;s session. More precisely, in the context of JupyterHub, this XSS could achieve the following:</p> <p>- Full access to JupyterHub API and user&#39;s single-user server, e.g. - Create and exfiltrate an API Token - Exfiltrate all files hosted on the user&#39;s single-user server: notebooks, images, etc. - Install malicious extensions. They can be used as a backdoor to silently regain access to victim&#39;s session anytime.</p> <p>### Patches</p> <p>To prevent cookie-tossing:</p> <p>- Upgrade to JupyterHub 4.1 (both hub and user environment) - enable per-user domains via `c.JupyterHub.subdomain_host = &#34;https://mydomain.example.org&#34;` - set `c.JupyterHub.cookie_host_prefix_enabled = True` to enable domain-locked cookies</p> <p>or, if available (applies to earlier JupyterHub versions):</p> <p>- deploy jupyterhub on its own domain, not shared with any other services - enable per-user domains via `c.JupyterHub.subdomain_host = &#34;https://mydomain.example.org&#34;`</p> <p><strong>Affected:</strong> PyPI: jupyterhub</p> <p>### Impact</p> <p>Affected configurations:</p> <p>- Single-origin JupyterHub deployments - JupyterHub deployments with user-controlled applications running on subdomains or peer subdomains of either the Hub or a single-user server.</p> <p>By tricking a user into visiting a malicious subdomain, the attacker can achieve an XSS directly affecting the former&#39;s session. More precisely, in the context of JupyterHub, this XSS could achieve the following:</p> <p>- Full access to JupyterHub API and user&#39;s single-user server, e.g. - Create and exfiltrate an API Token - Exfiltrate all files hosted on the user&#39;s single-user server: notebooks, images, etc. - Install malicious extensions. They can be used as a backdoor to silently regain access to victim&#39;s session anytime.</p> <p>### Patches</p> <p>To prevent cookie-tossing:</p> <p>- Upgrade to JupyterHub 4.1 (both hub and user environment) - enable per-user domains via `c.JupyterHub.subdomain_host = &#34;https://mydomain.example.org&#34;` - set `c.JupyterHub.cookie_host_prefix_enabled = True` to enable domain-locked cookies</p> <p>or, if available (applies to earlier JupyterHub versions):</p> <p>- deploy jupyterhub on its own domain, not shared with any other services - enable per-user domains via `c.JupyterHub.subdomain_host = &#34;https://mydomain.example.org&#34;`</p> https://cve.radiocsirt.org/vuln/ghsa-7r3h-4ph8-w38g