MediumGHSA-mg8j-w93w-xjgcCVE-2024-45440
Drupal Full Path Disclosure
Published 29 Aug 2024 · Updated 23 Apr 2025
Affected packages
drupal/drupalComposer
- Affected
- >=10.3.0 <10.3.6
- Fixed in
- 10.3.6
Update to the fixed version for your release line, for example:
composer require drupal/drupal:^10.3.6drupal/drupalComposer
- Affected
- >=11.0.0 <11.0.5
- Fixed in
- 11.0.5
Update to the fixed version for your release line, for example:
composer require drupal/drupal:^11.0.5drupal/core-recommendedComposer
- Affected
- >=10.3.0 <10.3.6
- Fixed in
- 10.3.6
Update to the fixed version for your release line, for example:
composer require drupal/core-recommended:^10.3.6drupal/core-recommendedComposer
- Affected
- >=11.0.0 <11.0.5
- Fixed in
- 11.0.5
Update to the fixed version for your release line, for example:
composer require drupal/core-recommended:^11.0.5drupal/coreComposer
- Affected
- >=10.3.0 <10.3.6
- Fixed in
- 10.3.6
Update to the fixed version for your release line, for example:
composer require drupal/core:^10.3.6drupal/coreComposer
- Affected
- >=11.0.0 <11.0.5
- Fixed in
- 11.0.5
Update to the fixed version for your release line, for example:
composer require drupal/core:^11.0.5drupal/drupalComposer
- Affected
- >=8.0.0 <10.2.9
- Fixed in
- 10.2.9
Update to the fixed version for your release line, for example:
composer require drupal/drupal:^10.2.9drupal/core-recommendedComposer
- Affected
- >=8.0.0 <10.2.9
- Fixed in
- 10.2.9
Update to the fixed version for your release line, for example:
composer require drupal/core-recommended:^10.2.9drupal/coreComposer
- Affected
- >=8.0.0 <10.2.9
- Fixed in
- 10.2.9
Update to the fixed version for your release line, for example:
composer require drupal/core:^10.2.9Details
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.
Is GHSA-mg8j-w93w-xjgc in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected drupal/drupal, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2024-45440
- Linkgithub.com/github/advisory-database/pull/4827
- Packagegithub.com/drupal/drupal
- Linksenscybersecurity.nl/CVE-2024-45440-Explained
- Linkwww.drupal.org/project/drupal/issues/3457781
- Linkwww.drupal.org/project/drupal/releases/10.2.9
- Linkwww.drupal.org/project/drupal/releases/10.3.6
- Linkwww.drupal.org/project/drupal/releases/11.0.5
- Linkwww.exploit-db.com/exploits/52266
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.