What is CVE-2024-45440?

CVE-2024-45440 is a medium-severity security vulnerability in drupal/drupal (composer), affecting versions >= 11.0.0, < 11.0.5. It is fixed in 11.0.5, 10.3.6, 10.2.9.

How severe is CVE-2024-45440?

CVE-2024-45440 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 packages are affected by CVE-2024-45440?

drupal/drupal (composer) versions >= 11.0.0, = 11.0.0, = 11.0.0, < 11.0.5.

Is there a fix for CVE-2024-45440?

Yes. CVE-2024-45440 is fixed in 11.0.5, 10.3.6, 10.2.9. Upgrade to this version or later.

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

Whether CVE-2024-45440 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-45440 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-45440 in drupal/drupal | Intelligent Application Security

Q: How severe is CVE-2024-45440?

CVE-2024-45440 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 packages are affected by CVE-2024-45440?

drupal/drupal (composer) versions >= 11.0.0, = 11.0.0, = 11.0.0, < 11.0.5.

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

Yes. CVE-2024-45440 is fixed in 11.0.5, 10.3.6, 10.2.9. Upgrade to this version or later.

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

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

Upgrade: drupal/drupal to 11.0.5 or later, drupal/core-recommended to 11.0.5 or later, drupal/core to 11.0.5 or later, drupal/drupal to 10.3.6 or later, drupal/core-recommended to 10.3.6 or later, drupal/core to 10.3.6 or later, drupal/drupal to 10.2.9 or later, drupal/core-recommended to 10.2.9 or later, drupal/core to 10.2.9 or later.

Summary

core/authorize.php in Drupal 11.x-dev allows Full Path Disclosure (even when error logging is None) if the value of hash_salt is file_get_contents of a file that does not exist.

Impact

CVE-2024-45440 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 (11.0.5, 10.3.6, 10.2.9); upgrading removes the vulnerable code path.

Affected versions

drupal/drupal (>= 11.0.0, < 11.0.5) drupal/core-recommended (>= 11.0.0, < 11.0.5) drupal/core (>= 11.0.0, < 11.0.5) drupal/drupal (>= 10.3.0, < 10.3.6) drupal/core-recommended (>= 10.3.0, < 10.3.6) drupal/core (>= 10.3.0, < 10.3.6) drupal/drupal (>= 8.0.0, < 10.2.9) drupal/core-recommended (>= 8.0.0, < 10.2.9) drupal/core (>= 8.0.0, < 10.2.9)

Security releases

drupal/drupal → 11.0.5 (composer) drupal/core-recommended → 11.0.5 (composer) drupal/core → 11.0.5 (composer) drupal/drupal → 10.3.6 (composer) drupal/core-recommended → 10.3.6 (composer) drupal/core → 10.3.6 (composer) drupal/drupal → 10.2.9 (composer) drupal/core-recommended → 10.2.9 (composer) drupal/core → 10.2.9 (composer)

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.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

drupal/drupal to 11.0.5 or later; drupal/core-recommended to 11.0.5 or later; drupal/core to 11.0.5 or later; drupal/drupal to 10.3.6 or later; drupal/core-recommended to 10.3.6 or later; drupal/core to 10.3.6 or later; drupal/drupal to 10.2.9 or later; drupal/core-recommended to 10.2.9 or later; drupal/core to 10.2.9 or later

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

Frequently Asked Questions

What is CVE-2024-45440? CVE-2024-45440 is a medium-severity security vulnerability in drupal/drupal (composer), affecting versions >= 11.0.0, < 11.0.5. It is fixed in 11.0.5, 10.3.6, 10.2.9.
How severe is CVE-2024-45440? CVE-2024-45440 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 packages are affected by CVE-2024-45440?
- drupal/drupal (composer) (versions >= 11.0.0, < 11.0.5)
- drupal/core-recommended (composer) (versions >= 11.0.0, < 11.0.5)
- drupal/core (composer) (versions >= 11.0.0, < 11.0.5)
Is there a fix for CVE-2024-45440? Yes. CVE-2024-45440 is fixed in 11.0.5, 10.3.6, 10.2.9. Upgrade to this version or later.
Is CVE-2024-45440 exploitable, and should I be worried? Whether CVE-2024-45440 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-45440 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-45440?
- Upgrade drupal/drupal to 11.0.5 or later
- Upgrade drupal/core-recommended to 11.0.5 or later
- Upgrade drupal/core to 11.0.5 or later
- Upgrade drupal/drupal to 10.3.6 or later
- Upgrade drupal/core-recommended to 10.3.6 or later
- Upgrade drupal/core to 10.3.6 or later
- Upgrade drupal/drupal to 10.2.9 or later
- Upgrade drupal/core-recommended to 10.2.9 or later
- Upgrade drupal/core to 10.2.9 or later

Other vulnerabilities in drupal/drupal

CVE-2024-55636 CVE-2024-55638 CVE-2024-55637 CVE-2024-55634 CVE-2024-12393