What is CVE-2024-28718?

CVE-2024-28718 is a medium-severity security vulnerability in magnum (pip), affecting versions < 14.1.2. It is fixed in 14.1.2, 17.0.2, 16.0.2, 15.0.2.

How severe is CVE-2024-28718?

CVE-2024-28718 has a CVSS score of 6.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 magnum are affected by CVE-2024-28718?

magnum (pip) versions < 14.1.2 is affected.

Is there a fix for CVE-2024-28718?

Yes. CVE-2024-28718 is fixed in 14.1.2, 17.0.2, 16.0.2, 15.0.2. Upgrade to this version or later.

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

Whether CVE-2024-28718 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-28718 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.

CVE-2024-28718 in magnum

Q: How severe is CVE-2024-28718?

CVE-2024-28718 has a CVSS score of 6.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 magnum are affected by CVE-2024-28718?

magnum (pip) versions < 14.1.2 is affected.

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

Yes. CVE-2024-28718 is fixed in 14.1.2, 17.0.2, 16.0.2, 15.0.2. Upgrade to this version or later.

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

Whether CVE-2024-28718 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-28718 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-28718?

Upgrade: magnum to 14.1.2 or later, magnum to 17.0.2 or later, magnum to 16.0.2 or later, magnum to 15.0.2 or later.

Summary

OpenStack magnum vulnerable to time-of-check to time-of-use (TOCTOU) attack

An issue in OpenStack magnum yoga-eom version allows a remote attacker to execute arbitrary code via the cert_manager.py. component.

Impact

CVE-2024-28718 has a CVSS score of 6.3 (Medium). The vector is requires local access, low 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 (14.1.2, 17.0.2, 16.0.2, 15.0.2); upgrading removes the vulnerable code path.

Affected versions

magnum (< 14.1.2) magnum (>= 17.0.0.0rc1, < 17.0.2) magnum (>= 16.0.0.0rc1, < 16.0.2) magnum (>= 15.0.0.0rc1, < 15.0.2)

Security releases

magnum → 14.1.2 (pip) magnum → 17.0.2 (pip) magnum → 16.0.2 (pip) magnum → 15.0.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

Upgrade the following packages to resolve this vulnerability:

magnum to 14.1.2 or later; magnum to 17.0.2 or later; magnum to 16.0.2 or later; magnum to 15.0.2 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-28718? CVE-2024-28718 is a medium-severity security vulnerability in magnum (pip), affecting versions < 14.1.2. It is fixed in 14.1.2, 17.0.2, 16.0.2, 15.0.2.
How severe is CVE-2024-28718? CVE-2024-28718 has a CVSS score of 6.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 magnum are affected by CVE-2024-28718? magnum (pip) versions < 14.1.2 is affected.
Is there a fix for CVE-2024-28718? Yes. CVE-2024-28718 is fixed in 14.1.2, 17.0.2, 16.0.2, 15.0.2. Upgrade to this version or later.
Is CVE-2024-28718 exploitable, and should I be worried? Whether CVE-2024-28718 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-28718 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-28718?
- Upgrade magnum to 14.1.2 or later
- Upgrade magnum to 17.0.2 or later
- Upgrade magnum to 16.0.2 or later
- Upgrade magnum to 15.0.2 or later