What is CVE-2024-28188?

CVE-2024-28188 is a medium-severity improper authentication vulnerability in jupyter-scheduler (pip), affecting versions >= 1.0.0, < 1.1.6. It is fixed in 1.1.6, 1.2.1, 1.8.2, 2.5.2. The application does not adequately verify the identity of a user, device, or process before granting access.

How severe is CVE-2024-28188?

CVE-2024-28188 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of jupyter-scheduler are affected by CVE-2024-28188?

jupyter-scheduler (pip) versions >= 1.0.0, < 1.1.6 is affected.

Is there a fix for CVE-2024-28188?

Yes. CVE-2024-28188 is fixed in 1.1.6, 1.2.1, 1.8.2, 2.5.2. Upgrade to this version or later.

Is CVE-2024-28188 exploitable, and should I be worried?

Whether CVE-2024-28188 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-28188 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-28188?

Upgrade: jupyter-scheduler to 1.1.6 or later, jupyter-scheduler to 1.2.1 or later, jupyter-scheduler to 1.8.2 or later, jupyter-scheduler to 2.5.2 or later.

CVE-2024-28188 in jupyter-scheduler

Q: How severe is CVE-2024-28188?

CVE-2024-28188 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of jupyter-scheduler are affected by CVE-2024-28188?

jupyter-scheduler (pip) versions >= 1.0.0, < 1.1.6 is affected.

Q: Is there a fix for CVE-2024-28188?

Yes. CVE-2024-28188 is fixed in 1.1.6, 1.2.1, 1.8.2, 2.5.2. Upgrade to this version or later.

Q: Is CVE-2024-28188 exploitable, and should I be worried?

Whether CVE-2024-28188 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-28188 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-28188?

Upgrade: jupyter-scheduler to 1.1.6 or later, jupyter-scheduler to 1.2.1 or later, jupyter-scheduler to 1.8.2 or later, jupyter-scheduler to 2.5.2 or later.

Summary

jupyter-scheduler's endpoint is missing authentication

Workarounds

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]. Please do not create a public GitHub issue.

[1] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting

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

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2024-28188 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.1.6, 1.2.1, 1.8.2, 2.5.2); upgrading removes the vulnerable code path.

Affected versions

jupyter-scheduler (>= 1.0.0, < 1.1.6) jupyter-scheduler (= 1.2.0) jupyter-scheduler (>= 1.3.0, < 1.8.2) jupyter-scheduler (>= 2.0.0, < 2.5.2)

Security releases

jupyter-scheduler → 1.1.6 (pip) jupyter-scheduler → 1.2.1 (pip) jupyter-scheduler → 1.8.2 (pip) jupyter-scheduler → 2.5.2 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

jupyter-scheduler==1.1.6
jupyter-scheduler==1.2.1
jupyter-scheduler==1.8.2
jupyter-scheduler==2.5.2

Frequently Asked Questions

What is CVE-2024-28188? CVE-2024-28188 is a medium-severity improper authentication vulnerability in jupyter-scheduler (pip), affecting versions >= 1.0.0, < 1.1.6. It is fixed in 1.1.6, 1.2.1, 1.8.2, 2.5.2. The application does not adequately verify the identity of a user, device, or process before granting access.
How severe is CVE-2024-28188? CVE-2024-28188 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of jupyter-scheduler are affected by CVE-2024-28188? jupyter-scheduler (pip) versions >= 1.0.0, < 1.1.6 is affected.
Is there a fix for CVE-2024-28188? Yes. CVE-2024-28188 is fixed in 1.1.6, 1.2.1, 1.8.2, 2.5.2. Upgrade to this version or later.
Is CVE-2024-28188 exploitable, and should I be worried? Whether CVE-2024-28188 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-28188 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-28188?
- Upgrade jupyter-scheduler to 1.1.6 or later
- Upgrade jupyter-scheduler to 1.2.1 or later
- Upgrade jupyter-scheduler to 1.8.2 or later
- Upgrade jupyter-scheduler to 2.5.2 or later