generated from druxt/quickstart-druxt-serverless
-
Notifications
You must be signed in to change notification settings - Fork 0
Update dependency drupal/core-recommended to v10 [SECURITY] #22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
develop
Choose a base branch
from
renovate/packagist-drupal-core-recommended-vulnerability
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update dependency drupal/core-recommended to v10 [SECURITY] #22
renovate
wants to merge
1
commit into
develop
from
renovate/packagist-drupal-core-recommended-vulnerability
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
42b6944
to
1619576
Compare
1619576
to
c2019c4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
9.3.6
->10.2.11
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 ofhash_salt
isfile_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
v9.3.7
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.
This PR was generated by Mend Renovate. View the repository job log.