{"answers":{"affected":"3 open source packages ship an affected version, including jupyterhub-kubespawner. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15110 in the wild and no public exploit code.","fix":"Upgrade jupyterhub-kubespawner to 0.12.0 or later.","what":"CVE-2020-15110 is a medium-severity missing authorization vulnerability in jupyterhub kubespawner, published on 17 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-15110 and fix it if it is affected.\n\nWhat it is: CVE-2020-15110 is a medium-severity missing authorization vulnerability in jupyterhub kubespawner, published on 17 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-15110 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- jupyterhub-kubespawner (PyPI): affected all versions; fixed in 0.12.0\n- jupyterhub-kubespawner (PyPI): affected all versions; fixed in 0.12.0\n- jupyterhub-kubespawner (PyPI): affected all versions; fixed in 0.12.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-2020-15110/ (Markdown: https://insights.sbomify.com/CVE-2020-15110/index.md)","id":"CVE-2020-15110","markdown":"https://insights.sbomify.com/CVE-2020-15110/index.md","name":"CVE-2020-15110","record":{"aliases":["GHSA-v7m9-9497-p9gr","PYSEC-2020-51"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"JupyterHub Kubernetes Spawner","requires_auth":"low_privilege","summary":"Attackers can craft server names to access other users' default servers, leading to unauthorized access and privilege escalation in JupyterHub environments.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"kubespawner","vendor":"jupyterhub"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"In jupyterhub-kubespawner before 0.12, certain usernames will be able to craft particular server names which will grant them access to the default server of other users who have matching usernames. This has been fixed in 0.12.","ecosystems":["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":"Possible pod name collisions in jupyterhub-kubespawner","id":"CVE-2020-15110","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":3,"n_references":2,"next":{"headline":"CRLF vulnerability in Fiber","id":"CVE-2020-15111"},"packages":[{"ecosystem":"PyPI","fixed":["0.12.0"],"introduced":["0"],"last_affected":[],"package":"jupyterhub-kubespawner","purl":null,"source":"GHSA-v7m9-9497-p9gr"},{"ecosystem":"PyPI","fixed":["0.12.0"],"introduced":["0"],"last_affected":[],"package":"jupyterhub-kubespawner","purl":"pkg:pypi/jupyterhub-kubespawner","source":"GHSA-v7m9-9497-p9gr"},{"ecosystem":"PyPI","fixed":["0.12.0"],"introduced":["0"],"last_affected":[],"package":"jupyterhub-kubespawner","purl":"pkg:pypi/jupyterhub-kubespawner","source":"PYSEC-2020-51"}],"prev":{"headline":"Ability to change order address without triggering address validations in solidus","id":"CVE-2020-15109"},"products":["kubespawner"],"published":"2020-07-17","related":[],"sources":[{"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":["jupyterhub"]},"summary":"Attackers can craft server names to access other users' default servers, leading to unauthorized access and privilege escalation in JupyterHub environments.","url":"https://insights.sbomify.com/CVE-2020-15110/"}