jupyter-scheduler
Affected
- introduced
1.0.0, fixed1.1.6(ecosystem)
Fixed versions
1.1.6
Fix
- Fixed version
1.1.6pip install --upgrade jupyter-scheduler==1.1.6
Advisory
Also known as: CVE-2024-28188, PYSEC-2026-1479
jupyter-scheduler's endpoint is missing authentication
Impact
jupyter_scheduler is missing an authentication check in Jupyter Server on an API endpoint (GET /scheduler/runtime_environments) which lists the names of the Conda environments on the server. In affected versions, jupyter_scheduler allows an unauthenticated user to obtain the list of Conda environment names on the server. This reveals any information that may be present in a Conda environment name.
This issue does not allow an unauthenticated third party to read, modify, or enter the Conda environments present on the server where jupyter_scheduler is running. This issue only reveals the list of Conda environment names.
Impacted versions: >=1.0.0,<=1.1.5 ; ==1.2.0 ; >=1.3.0,<=1.8.1 ; >=2.0.0,<=2.5.1
Patches
jupyter-scheduler==1.1.6jupyter-scheduler==1.2.1jupyter-scheduler==1.8.2jupyter-scheduler==2.5.2Workarounds
Server operators who are unable to upgrade can disable the jupyter-scheduler extension with:
jupyter server extension disable jupyter-scheduler
References
If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [1] or directly via email to [[email protected]](mailto:[email protected]). Please do not create a public GitHub issue.
[1] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting
Medium Basis: The source's own band: MODERATE
1.0.0, fixed 1.1.6 (ecosystem)1.1.6
1.1.6pip install --upgrade jupyter-scheduler==1.1.61.2.0, fixed 1.2.1 (ecosystem)1.2.1
1.2.1pip install --upgrade jupyter-scheduler==1.2.11.3.0, fixed 1.8.2 (ecosystem)1.8.2
1.8.2pip install --upgrade jupyter-scheduler==1.8.22.0.0, fixed 2.5.2 (ecosystem)2.5.2
2.5.2pip install --upgrade jupyter-scheduler==2.5.2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0