{"answers":{"affected":"4 open source packages ship an affected version, including jupyterhub. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36191 in the wild and no public exploit code.","fix":"Upgrade jupyterhub to a fixed version for your release line: 1.1.1 or 1.2.0b1.","what":"CVE-2020-36191 is a medium-severity vulnerability in n/a, published on 13 Jan 2021. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-36191 and fix it if it is affected.\n\nWhat it is: CVE-2020-36191 is a medium-severity vulnerability in n/a, published on 13 Jan 2021. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-36191 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- jupyterhub (Bitnami): affected from 1.1.0; fixed in 1.1.1\n- jupyterhub (PyPI): affected all versions; fixed in 1.2.0b1\n- jupyterhub (PyPI): affected all versions; fixed in 1.2.0b1\n- jupyterhub (PyPI): affected all versions; fixed in 1.2.0b1\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-2020-36191/ (Markdown: https://insights.sbomify.com/CVE-2020-36191/index.md)","id":"CVE-2020-36191","markdown":"https://insights.sbomify.com/CVE-2020-36191/index.md","name":"CVE-2020-36191","record":{"aliases":["BIT-jupyterhub-2020-36191","DEBIAN-CVE-2020-36191","GHSA-7xx3-qp5w-fw96","PYSEC-2021-67","UBUNTU-CVE-2020-36191"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"JupyterHub","requires_auth":"high_privilege","summary":"Attackers can perform unauthorized admin actions like adding or removing users in JupyterHub due to missing CSRF protection.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jupyterhub","vendor":"jupyter"}],"cvss":{"score":4.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"JupyterHub 1.1.0 allows CSRF in the admin panel via a request that lacks an _xsrf field, as demonstrated by a /hub/api/user request (to add or remove a user account).","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":"Cross-Site Request Forgery in JupyterHub","id":"CVE-2020-36191","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"csrf","year":"2020"},"n_packages":4,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2020-36192"},"packages":[{"ecosystem":"Bitnami","fixed":["1.1.1"],"introduced":["1.1.0"],"last_affected":[],"package":"jupyterhub","purl":"pkg:bitnami/jupyterhub","source":"BIT-jupyterhub-2020-36191"},{"ecosystem":"PyPI","fixed":["1.2.0b1"],"introduced":["0"],"last_affected":[],"package":"jupyterhub","purl":null,"source":"GHSA-7xx3-qp5w-fw96"},{"ecosystem":"PyPI","fixed":["1.2.0b1"],"introduced":["0"],"last_affected":[],"package":"jupyterhub","purl":"pkg:pypi/jupyterhub","source":"GHSA-7xx3-qp5w-fw96"},{"ecosystem":"PyPI","fixed":["1.2.0b1"],"introduced":["0"],"last_affected":[],"package":"jupyterhub","purl":"pkg:pypi/jupyterhub","source":"PYSEC-2021-67"}],"prev":{"headline":"rails_admin ruby gem XSS vulnerability","id":"CVE-2020-36190"},"products":["n/a"],"published":"2021-01-13","related":[{"cvss_score":8.1,"headline":"XSS in JupyterHub via Self-XSS leveraged by Cookie Tossing","id":"CVE-2024-28233","kev_date_added":null,"published":"2024-03-27"},{"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":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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can perform unauthorized admin actions like adding or removing users in JupyterHub due to missing CSRF protection.","url":"https://insights.sbomify.com/CVE-2020-36191/"}