View online: https://www.drupal.org/sa-core-2024-006
Project: Drupal core [1]
Date: 2024-November-20
Security risk: *Less critical* 8 ∕ 25
AC:Complex/A:User/CI:None/II:Some/E:Theoretical/TD:Uncommon [2]
Vulnerability: Gadget chain
Affected versions: >= 8.0.0 < 10.2.11 || >= 10.3.0 < 10.3.9 || >= 11.0.0 <
11.0.8
Description:
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.
Solution:
Install the latest version:
* If you are using Drupal 10.2, update to Drupal 10.2.11. [3]
* If you are using Drupal 10.3, update to Drupal 10.3.9. [4]
* If you are using Drupal 11.0, update to Drupal 11.0.8. [5]
* Drupal 7 is not affected.
All versions of Drupal 10 prior to 10.2 are end-of-life and do not receive
security coverage. (Drupal 8 [6] and Drupal 9 [7] have both reached
end-of-life.)
Reported By:
* Drew Webber [8] of the Drupal Security Team
Fixed By:
* Drew Webber [9] of the Drupal Security Team
* Lee Rowlands [10] of the Drupal Security Team
Coordinated By:
* Juraj Nemec [11] of the Drupal Security Team
* Benji Fisher [12] of the Drupal Security Team
* xjm [13] of the Drupal Security Team
[1] https://www.drupal.org/project/drupal
[2] https://www.drupal.org/security-team/risk-levels
[3] https://www.drupal.org/project/drupal/releases/10.2.11
[4] https://www.drupal.org/project/drupal/releases/10.3.9
[5] https://www.drupal.org/project/drupal/releases/11.0.8
[6] https://www.drupal.org/psa-2021-06-29
[7] https://www.drupal.org/psa-2023-11-01
[8] https://www.drupal.org/user/255969
[9] https://www.drupal.org/user/255969
[10] https://www.drupal.org/user/395439
[11] https://www.drupal.org/user/272316
[12] https://www.drupal.org/user/683300
[13] https://www.drupal.org/u/xjm
View online: https://www.drupal.org/sa-core-2024-007
Project: Drupal core [1]
Date: 2024-November-20
Security risk: *Moderately critical* 14 ∕ 25
AC:Complex/A:Admin/CI:All/II:All/E:Theoretical/TD:Uncommon [2]
Vulnerability: Gadget chain
Affected versions: >= 8.0.0 < 10.2.11 || >= 10.3.0 < 10.3.9 || >= 11.0.0 <
11.0.8
Description:
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.
Solution:
Install the latest version:
* If you are using Drupal 10.2, update to Drupal 10.2.11. [3]
* If you are using Drupal 10.3, update to Drupal 10.3.9. [4]
* If you are using Drupal 11.0, update to Drupal 11.0.8. [5]
* Drupal 7 is not affected.
All versions of Drupal 10 prior to 10.2 are end-of-life and do not receive
security coverage. (Drupal 8 [6] and Drupal 9 [7] have both reached
end-of-life.)
Reported By:
* Drew Webber [8] of the Drupal Security Team
Fixed By:
* Drew Webber [9] of the Drupal Security Team
* Lee Rowlands [10] of the Drupal Security Team
Coordinated By:
* Juraj Nemec [11] of the Drupal Security Team
* Greg Knaddison [12] of the Drupal Security Team
* Benji Fisher [13] of the Drupal Security Team
* xjm [14] of the Drupal Security Team
[1] https://www.drupal.org/project/drupal
[2] https://www.drupal.org/security-team/risk-levels
[3] https://www.drupal.org/project/drupal/releases/10.2.11
[4] https://www.drupal.org/project/drupal/releases/10.3.9
[5] https://www.drupal.org/project/drupal/releases/11.0.8
[6] https://www.drupal.org/psa-2021-06-29
[7] https://www.drupal.org/psa-2023-11-01
[8] https://www.drupal.org/user/255969
[9] https://www.drupal.org/user/255969
[10] https://www.drupal.org/user/395439
[11] https://www.drupal.org/user/272316
[12] https://www.drupal.org/user/36762
[13] https://www.drupal.org/user/683300
[14] https://www.drupal.org/u/xjm
View online: https://www.drupal.org/sa-contrib-2024-055
Project: Cookiebot + GTM [1]
Date: 2024-October-30
Security risk: *Moderately critical* 14 ∕ 25
AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2]
Vulnerability: Cross Site Scripting
Affected versions: <1.0.18
Description:
This module makes it possible for you to integrate Cookiebot and Google Tag
Manager in a fast and simple way.
The module doesn't sufficiently filter for malicious script leading to a
persistent cross site scripting (XSS) vulnerability.
Solution:
Install the latest version and review settings:
1) If you use the Cookiebot + GTM module for Drupal, upgrade to Cookiebot +
GTM 1.0.18 [3]
2) Additionally, the new codebase adds validation and permission changes so
admins should re-save the configuration form at
/admin/config/cookiebot_gtm and confirm which roles have permission to
configure the module at /admin/people/permissions.
Reported By:
* Pierre Rudloff [4]
Fixed By:
* Fabian de Rijk [5]
Coordinated By:
* Greg Knaddison [6] of the Drupal Security Team
* Juraj Nemec [7] of the Drupal Security Team
* Cathy Theys [8] of the Drupal Security Team
[1] https://www.drupal.org/project/cookiebot_gtm
[2] https://www.drupal.org/security-team/risk-levels
[3] https://www.drupal.org/project/cookiebot_gtm/releases/1.0.18
[4] https://www.drupal.org/user/3611858
[5] https://www.drupal.org/user/278745
[6] https://www.drupal.org/user/36762
[7] https://www.drupal.org/user/272316
[8] https://www.drupal.org/u/yesct