jupyter-scheduler's endpoint is missing authentication
jupyter-server jupyter-scheduler
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| jupyter-scheduler PyPI |
|
|
jupyter-server jupyter-scheduler
| Product | Affected | Fixed in |
|---|---|---|
| jupyter-scheduler PyPI |
|
|
Jupyter Scheduler is collection of extensions for programming jobs to run now or run on a schedule. The list of conda environments of `jupyter-scheduler` users maybe be exposed, potentially revealing information about projects that a specific user may be working on. This vulnerability has been patched in version(s) 1.1.6, 1.2.1, 1.8.2 and 2.5.2.
From the CVE record · GitHub_M
Jupyter Scheduler may expose a user's list of conda environments, potentially revealing information about their projects. The input does not specify whether access is remote or local, whether authentication is required, or whether user interaction is needed.
Anyone running the PyPI jupyter-scheduler package should check installations in the affected ranges: >=1.0.0 <1.1.6, >=1.2.0 <1.2.1, >=1.3.0 <1.8.2, or >=2.0.0 <2.5.2.