chore(deps): update dependency drupal/core-recommended to v10 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
drupal/core-recommended	^9.3 -> ^10.0

GitHub Vulnerability Alerts

CVE-2024-45440

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.

CVE-2024-55637

Drupal core contains a potential PHP Object Injection vulnerability that (if combined with another exploit) could lead to Remote Code Execution. It is not directly exploitable.

This issue is mitigated by the fact that in order for it to be exploitable, a separate vulnerability must be present to allow an attacker to pass unsafe input to unserialize(). There are no such known exploits in Drupal core.

To help protect against this potential vulnerability, types have been added to properties in some of Drupal core's classes. If an application extends those classes, the same types may need to be specified on the subclass to avoid a TypeError.

This issue affects Drupal Core: from 8.0.0 before 10.2.11, from 10.3.0 before 10.3.9, from 11.0.0 before 11.0.8.

CVE-2024-55636

Drupal core contains a potential PHP Object Injection vulnerability that (if combined with another exploit) could lead to Artbitrary File Deletion. It is not directly exploitable.

This issue is mitigated by the fact that in order to be exploitable, a separate vulnerability must be present that allows an attacker to pass unsafe input to unserialize(). There are no such known exploits in Drupal core.

To help protect against this vulnerability, types have been added to properties in some of Drupal core's classes. If an application extends those classes, the same types may need to be specified on the subclass to avoid a TypeError.

This issue affects Drupal Core: from 8.0.0 before 10.2.11, from 10.3.0 before 10.3.9, from 11.0.0 before 11.0.8.

CVE-2024-55634

Drupal's uniqueness checking for certain user fields is inconsistent depending on the database engine and its collation. As a result, a user may be able to register with the same email address as another user. This may lead to data integrity issues. This issue affects Drupal Core: from 8.0.0 before 10.2.11, from 10.3.0 before 10.3.9, from 11.0.0 before 11.0.8.

CVE-2024-12393

Drupal uses JavaScript to render status messages in some cases and configurations. In certain situations, the status messages are not adequately sanitized. This issue affects Drupal Core: from 8.8.0 before 10.2.11, from 10.3.0 before 10.3.9, from 11.0.0 before 11.0.8.

CVE-2024-55638

Drupal core contains a potential PHP Object Injection vulnerability that (if combined with another exploit) could lead to Remote Code Execution. It is not directly exploitable.

This issue is mitigated by the fact that in order for it to be exploitable, a separate vulnerability must be present to allow an attacker to pass unsafe input to unserialize(). There are no such known exploits in Drupal core.

To help protect against this potential vulnerability, some additional checks have been added to Drupal core's database code. If you use a third-party database driver, check the release notes for additional configuration steps that may be required in certain cases.

This issue affects Drupal Core: from 7.0 before 7.102, from 8.0.0 before 10.2.11, from 10.3.0 before 10.3.9.

---

Release Notes

drupal/core-recommended (drupal/core-recommended)

v10.2.11

Compare Source

v10.2.10

Compare Source

v10.2.9

Compare Source

v10.2.8

Compare Source

v10.2.7

Compare Source

v10.2.6

Compare Source

v10.2.5

Compare Source

v10.2.4

Compare Source

v10.2.3

Compare Source

v10.2.2

Compare Source

v10.2.1

Compare Source

v10.2.0

Compare Source

v10.1.8

Compare Source

v10.1.7

Compare Source

v10.1.6

Compare Source

v10.1.5

Compare Source

v10.1.4

Compare Source

v10.1.3

Compare Source

v10.1.2

Compare Source

v10.1.1

Compare Source

v10.1.0

Compare Source

v10.0.11

Compare Source

v10.0.10

Compare Source

v10.0.9

Compare Source

v10.0.8

Compare Source

v10.0.7

Compare Source

v10.0.6

Compare Source

v10.0.5

Compare Source

v10.0.4

Compare Source

v10.0.3

Compare Source

v10.0.2

Compare Source

v10.0.1

Compare Source

v10.0.0

Compare Source

v9.5.11

Compare Source

v9.5.10

Compare Source

v9.5.9

Compare Source

v9.5.8

Compare Source

v9.5.7

Compare Source

v9.5.6

Compare Source

v9.5.5

Compare Source

v9.5.4

Compare Source

v9.5.3

Compare Source

v9.5.2

Compare Source

v9.5.1

Compare Source

v9.5.0

Compare Source

v9.4.15

Compare Source

v9.4.14

Compare Source

v9.4.13

Compare Source

v9.4.12

Compare Source

v9.4.11

Compare Source

v9.4.10

Compare Source

v9.4.9

Compare Source

v9.4.8

Compare Source

v9.4.7

Compare Source

v9.4.6

Compare Source

v9.4.5

Compare Source

v9.4.4

Compare Source

v9.4.3

Compare Source

v9.4.2

Compare Source

v9.4.1

Compare Source

v9.4.0

Compare Source

v9.3.22

Compare Source

v9.3.21

Compare Source

v9.3.20

Compare Source

v9.3.19

Compare Source

v9.3.18

Compare Source

v9.3.17

Compare Source

v9.3.16

Compare Source

v9.3.15

Compare Source

v9.3.14

Compare Source

v9.3.13

Compare Source

v9.3.12

Compare Source

v9.3.11

Compare Source

v9.3.10

Compare Source

v9.3.9

Compare Source

v9.3.8

Compare Source

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: composer.lock

Command failed: composer update drupal/core-recommended:10.2.11 --with-dependencies --ignore-platform-req='ext-*' --ignore-platform-req='lib-*' --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins --minimal-changes
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/core-recommended ^10.0 -> satisfiable by drupal/core-recommended[10.2.11].
    - drupal/core-recommended 10.2.11 requires drupal/core 10.2.11 -> found drupal/core[10.2.11] but these were not loaded, likely because it conflicts with another require.
  Problem 2
    - drupal/admin_audit_trail is locked to version 1.0.0-beta1 and an update of this package was not requested.
    - drupal/admin_audit_trail 1.0.0-beta1 requires drupal/core ^8 || ^9 -> satisfiable by drupal/core[8.0.0-beta6, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev].
    - drupal/core[9.3.0-alpha1, ..., 9.4.0-alpha1] require laminas/laminas-diactoros ^2.1 -> satisfiable by laminas/laminas-diactoros[2.1.0, ..., 2.26.x-dev], longwave/laminas-diactoros[2.14.1, 2.14.2, 2.14.3, 2.14.x-dev].
    - drupal/core[9.4.0-beta1, ..., 9.4.14] require laminas/laminas-diactoros ^2.11 -> satisfiable by laminas/laminas-diactoros[2.11.0, ..., 2.26.x-dev], longwave/laminas-diactoros[2.14.1, 2.14.2, 2.14.3, 2.14.x-dev].
    - drupal/core[9.4.15, ..., 9.5.x-dev] require longwave/laminas-diactoros ^2.14 -> satisfiable by longwave/laminas-diactoros[2.14.1, 2.14.2, 2.14.3, 2.14.x-dev].
    - drupal/core[9.5.0-beta1, ..., 9.5.8] require laminas/laminas-diactoros ^2.14 -> satisfiable by laminas/laminas-diactoros[2.14.0, ..., 2.26.x-dev], longwave/laminas-diactoros[2.14.1, 2.14.2, 2.14.3, 2.14.x-dev].
    - laminas/laminas-diactoros[2.1.0, ..., 2.4.x-dev] require php ^7.1 -> your php version (8.4.11) does not satisfy that requirement.
    - laminas/laminas-diactoros[2.7.0, ..., 2.14.x-dev] require php ^7.3 || ~8.0.0 || ~8.1.0 -> your php version (8.4.11) does not satisfy that requirement.
    - longwave/laminas-diactoros 2.14.1 require php ^7.3 || ~8.0.0 || ~8.1.0 -> your php version (8.4.11) does not satisfy that requirement.
    - laminas/laminas-diactoros[2.15.0, ..., 2.17.x-dev] require php ^7.4 || ~8.0.0 || ~8.1.0 -> your php version (8.4.11) does not satisfy that requirement.
    - laminas/laminas-diactoros[2.18.0, ..., 2.25.x-dev] require php ~8.0.0 || ~8.1.0 || ~8.2.0 -> your php version (8.4.11) does not satisfy that requirement.
    - laminas/laminas-diactoros[2.26.0, ..., 2.26.x-dev] require php ~8.0.0 || ~8.1.0 || ~8.2.0 || ~8.3.0 -> your php version (8.4.11) does not satisfy that requirement.
    - laminas/laminas-diactoros[2.5.0, ..., 2.6.x-dev] require php ^7.3 || ~8.0.0 -> your php version (8.4.11) does not satisfy that requirement.
    - longwave/laminas-diactoros 2.14.2 requires php ^7.3 || ~8.0.0 || ~8.1.0 || ~8.2.0 -> your php version (8.4.11) does not satisfy that requirement.
    - longwave/laminas-diactoros[2.14.3, ..., 2.14.x-dev] require php ^7.3 || ~8.0.0 || ~8.1.0 || ~8.2.0 || ~8.3.0 -> your php version (8.4.11) does not satisfy that requirement.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.