View online: https://www.drupal.org/sa-contrib-2024-064
Project: Tarte au Citron [1]
Date: 2024-November-27
Security risk: *Moderately critical* 13 ∕ 25
AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2]
Vulnerability: Cross Site Scripting
Affected versions: <2.0.5
Description:
This module integrates Tarte au citron JS library with Drupal and prevent
services to be loaded without user consent. Administrators can enable and
configure services which will be managed by Tarte au citron.
When Google Tag Manager (GTM) service is enabled, an attacker can load a GTM
container that can completely change the page or insert malicious JS.
This vulnerability is mitigated by the fact that the attacker must have a
role with the permission "administer tarte au citron".
Solution:
Install the latest version and confirm only trusted roles have the
"Administer Tarte au citron" permission.
* If you use the Tarte au citron module for Drupal 10.x, upgrade to Tarte
au
citron 2.0.5 [3]
Reported By:
* Pierre Rudloff [4]
Fixed By:
* Kévin Le lostec [5]
Coordinated By:
* Greg Knaddison [6] of the Drupal Security Team
* Juraj Nemec [7] of the Drupal Security Team
* cilefen [8] of the Drupal Security Team
[1] https://www.drupal.org/project/tarte_au_citron
[2] https://www.drupal.org/security-team/risk-levels
[3] https://www.drupal.org/project/tarte_au_citron/releases/2.0.5
[4] https://www.drupal.org/user/3611858
[5] https://www.drupal.org/user/3455737
[6] https://www.drupal.org/user/36762
[7] https://www.drupal.org/user/272316
[8] https://www.drupal.org/u/cilefen
View online: https://www.drupal.org/sa-contrib-2024-063
Project: Eloqua [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: Arbitrary PHP code execution
Description:
This module integrates webforms with eloqua, an automated marketing and
demand generation software built to improve the quality and quantity of
customers' sales leads and streamline their sales processes.
In certain cases the module doesn't sufficiently sanitize data before passing
it to PHP's unserialize() function, which could result in Remote Code
Execution via PHP Object Injection.
This vulnerability is mitigated by the fact that an attack must operate with
the permission "access administration pages", however this could be the case
if this issue were combined with others in an "attack chain".
Solution:
Install the latest version:
* If you use the Eloqua module for Drupal 7.x, upgrade to Eloqua 7.x-1.15
[3]
Reported By:
* Drew Webber [4] of the Drupal Security Team
Fixed By:
* Albert Volkman [5]
Coordinated By:
* Greg Knaddison [6] of the Drupal Security Team
[1] https://www.drupal.org/project/eloqua
[2] https://www.drupal.org/security-team/risk-levels
[3] https://www.drupal.org/project/eloqua/releases/7.x-1.15
[4] https://www.drupal.org/user/255969
[5] https://www.drupal.org/user/429502
[6] https://www.drupal.org/user/36762
View online: https://www.drupal.org/sa-contrib-2024-061
Project: Node export [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: Arbitrary PHP code execution
Description:
This module allows users to export nodes and then import it into another
Drupal installation, or on the same site.
In certain cases the module doesn't sufficiently sanitize data before passing
it to PHP's unserialize() function, which could results in Remote Code
Execution via PHP Object Injection.
This vulnerability is mitigated by the fact that an attack must operate with
the permission "Use PHP to import nodes", however this could be the case if
this issue were combined with others in an "attack chain".
In general, if this module is not in active use it is recommended to disable
it.
Solution:
Install the latest version:
* If you use the Node Export module for Drupal 7, upgrade to Node Export
7.x-3.3 [3]
Reported By:
* Drew Webber [4] of the Drupal Security Team
Fixed By:
* Drew Webber [5] of the Drupal Security Team
* Ivan Trokhanenko [6]
Coordinated By:
* Drew Webber [7] of the Drupal Security Team
* Greg Knaddison [8] of the Drupal Security Team
[1] https://www.drupal.org/project/node_export
[2] https://www.drupal.org/security-team/risk-levels
[3] https://www.drupal.org/project/node_export/releases/7.x-3.3
[4] https://www.drupal.org/user/255969
[5] https://www.drupal.org/user/255969
[6] https://www.drupal.org/user/3546872
[7] https://www.drupal.org/user/255969
[8] https://www.drupal.org/user/36762
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