{"answers":{"affected":"3 open source packages ship an affected version, including jupyterhub-systemdspawner. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26261 in the wild and no public exploit code.","fix":"Upgrade jupyterhub-systemdspawner to 0.15.0 or later.","what":"CVE-2020-26261 is a high-severity vulnerability in jupyterhub systemdspawner, published on 9 Dec 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-26261 and fix it if it is affected.\n\nWhat it is: CVE-2020-26261 is a high-severity vulnerability in jupyterhub systemdspawner, published on 9 Dec 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-26261 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- jupyterhub-systemdspawner (PyPI): affected all versions; fixed in 0.15.0\n- jupyterhub-systemdspawner (PyPI): affected all versions; fixed in 0.15.0\n- jupyterhub-systemdspawner (PyPI): affected all versions; fixed in 0.15.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-26261/ (Markdown: https://insights.sbomify.com/CVE-2020-26261/index.md)","id":"CVE-2020-26261","markdown":"https://insights.sbomify.com/CVE-2020-26261/index.md","name":"CVE-2020-26261","record":{"aliases":["GHSA-cg54-gpgr-4rm6","PYSEC-2020-52"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"JupyterHub systemd spawner","requires_auth":"low_privilege","summary":"Attackers can read user API tokens from systemd unit environments, potentially leading to account takeover in JupyterHub deployments.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"systemdspawner","vendor":"jupyterhub"}],"cvss":{"score":7.9,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"}],"description":"jupyterhub-systemdspawner enables JupyterHub to spawn single-user notebook servers using systemd. In jupyterhub-systemdspawner before version 0.15 user API tokens issued to single-user servers are specified in the environment of systemd units. These tokens are incorrectly accessible to all users. In particular, the-littlest-jupyterhub is affected, which uses systemdspawner by default. This is patched in jupyterhub-systemdspawner v0.15","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":"user-readable api tokens in systemd units","id":"CVE-2020-26261","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":3,"n_references":4,"next":{"headline":"Loopback bypass in Coturn","id":"CVE-2020-26262"},"packages":[{"ecosystem":"PyPI","fixed":["0.15.0"],"introduced":["0"],"last_affected":[],"package":"jupyterhub-systemdspawner","purl":null,"source":"GHSA-cg54-gpgr-4rm6"},{"ecosystem":"PyPI","fixed":["0.15.0"],"introduced":["0"],"last_affected":[],"package":"jupyterhub-systemdspawner","purl":"pkg:pypi/jupyterhub-systemdspawner","source":"GHSA-cg54-gpgr-4rm6"},{"ecosystem":"PyPI","fixed":["0.15.0"],"introduced":["0"],"last_affected":[],"package":"jupyterhub-systemdspawner","purl":"pkg:pypi/jupyterhub-systemdspawner","source":"PYSEC-2020-52"}],"prev":{"headline":"Server Side Request Forgery in BookStack","id":"CVE-2020-26260"},"products":["systemdspawner"],"published":"2020-12-09","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 read user API tokens from systemd unit environments, potentially leading to account takeover in JupyterHub deployments.","url":"https://insights.sbomify.com/CVE-2020-26261/"}