{"answers":{"affected":"4 open source packages ship an affected version, including jupyterhub. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-28233 in the wild and no public exploit code.","fix":"Upgrade jupyterhub to 4.1.0 or later.","what":"CVE-2024-28233 is a high-severity cross-site scripting vulnerability in jupyterhub, published on 27 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-28233 and fix it if it is affected.\n\nWhat it is: CVE-2024-28233 is a high-severity cross-site scripting vulnerability in jupyterhub, published on 27 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-28233 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- jupyterhub (Bitnami): affected all versions; fixed in 4.1.0\n- jupyterhub (PyPI): affected all versions; fixed in 4.1.0\n- jupyterhub (PyPI): affected all versions; fixed in 4.1.0\n- jupyterhub (PyPI): affected all versions; fixed in 4.1.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-28233/ (Markdown: https://insights.sbomify.com/CVE-2024-28233/index.md)","id":"CVE-2024-28233","markdown":"https://insights.sbomify.com/CVE-2024-28233/index.md","name":"CVE-2024-28233","record":{"aliases":["BIT-jupyterhub-2024-28233","DEBIAN-CVE-2024-28233","GHSA-7r3h-4ph8-w38g","PYSEC-2026-1480","UBUNTU-CVE-2024-28233"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"JupyterHub server","requires_auth":"none","summary":"Attackers can execute XSS via cookie tossing to gain full API access and take over user sessions in specific JupyterHub deployments.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"jupyterhub","vendor":"jupyter"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-565","name":"Reliance on Cookies without Validation and Integrity Checking"},{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"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's session. More precisely, in the context of JupyterHub, this XSS could achieve full access to JupyterHub API and user'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.","ecosystems":["Bitnami","PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"XSS in JupyterHub via Self-XSS leveraged by Cookie Tossing","id":"CVE-2024-28233","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"xss","year":"2024"},"n_packages":4,"n_references":2,"next":{"headline":"Contao has insufficient BBCode sanitizer","id":"CVE-2024-28234"},"packages":[{"ecosystem":"Bitnami","fixed":["4.1.0"],"introduced":["0"],"last_affected":[],"package":"jupyterhub","purl":"pkg:bitnami/jupyterhub","source":"BIT-jupyterhub-2024-28233"},{"ecosystem":"PyPI","fixed":["4.1.0"],"introduced":["0"],"last_affected":[],"package":"jupyterhub","purl":null,"source":"GHSA-7r3h-4ph8-w38g"},{"ecosystem":"PyPI","fixed":["4.1.0"],"introduced":["0"],"last_affected":[],"package":"jupyterhub","purl":"pkg:pypi/jupyterhub","source":"GHSA-7r3h-4ph8-w38g"},{"ecosystem":"PyPI","fixed":["4.1.0"],"introduced":["0"],"last_affected":[],"package":"jupyterhub","purl":"pkg:pypi/jupyterhub","source":"PYSEC-2026-1480"}],"prev":{"headline":"Username Enumeration in CasaOS via bypass of CVE-2024-24766","id":"CVE-2024-28232"},"products":["jupyterhub"],"published":"2024-03-27","related":[{"cvss_score":7.2,"headline":"JupyterHub has a privilege escalation vulnerability with the `admin:users` scope","id":"CVE-2024-41942","kev_date_added":null,"published":"2024-08-08"},{"cvss_score":6.1,"headline":"Open Redirect vulnerability in jupyterhub and notebook","id":"CVE-2019-10255","kev_date_added":null,"published":"2019-03-28"},{"cvss_score":5.4,"headline":"JupyterHub: Cross-origin form POSTs bypass XSRF","id":"CVE-2026-40864","kev_date_added":null,"published":"2026-05-22"},{"cvss_score":5.1,"headline":"JupyterHub has an Open Redirect Vulnerability","id":"CVE-2026-33709","kev_date_added":null,"published":"2026-04-03"},{"cvss_score":4.5,"headline":"Cross-Site Request Forgery in JupyterHub","id":"CVE-2020-36191","kev_date_added":null,"published":"2021-01-13"},{"cvss_score":3.5,"headline":"incomplete logout in JupyterHub","id":"CVE-2021-41247","kev_date_added":null,"published":"2021-11-04"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-15","vendors":["jupyterhub"]},"summary":"Attackers can execute XSS via cookie tossing to gain full API access and take over user sessions in specific JupyterHub deployments.","url":"https://insights.sbomify.com/CVE-2024-28233/"}