CVE-2024-28188PYSEC-2026-1479GHSA-V9G2-G7J4-4JXC
jupyter-scheduler's endpoint is missing authentication
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.1.6, 1.2.1, 1.8.2, 2.5.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- jupyter-server jupyter-scheduler
From 1.0.0 · through 1.1.5; From 1.3.0 · through 1.8.1; From 2.0.0 · through 2.5.1
- jupyter-schedulerPyPI
From 1.0.0 · fixed in 1.1.6; From 1.2.0 · fixed in 1.2.1; From 1.3.0 · fixed in 1.8.2; From 2.0.0 · fixed in 2.5.2
- jupyter-schedulerPyPI
From 1.0.0 · fixed in 1.1.6
- jupyter-schedulerPyPI
From 1.2.0 · fixed in 1.2.1
- jupyter-schedulerPyPI
From 1.3.0 · fixed in 1.8.2
- jupyter-schedulerPyPI
From 2.0.0 · fixed in 2.5.2