November 2024 - Security-news

Tarte au Citron - Moderately critical - Cross Site Scripting - SA-CONTRIB-2024-064
by security-news＠drupal.org 27 Nov '24

27 Nov '24

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

1 0

Eloqua - Moderately critical - Arbitrary PHP code execution - SA-CONTRIB-2024-063
by security-news＠drupal.org 20 Nov '24

20 Nov '24

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

1 0

Mailjet - Moderately critical - Arbitrary PHP code execution - SA-CONTRIB-2024-062
by security-news＠drupal.org 20 Nov '24

20 Nov '24

View online: https://www.drupal.org/sa-contrib-2024-062 Project: Mailjet [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 Affected versions: <4.0.1 Description: This module for Drupal provides complete control of Email settings with Drupal and Mailjet. In certain cases the module doesn't securely pass data 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 "administer mailjet module", however this could be the case if this issue were combined with others in an "attack chain". Solution: Install the latest version: * Upgrade to Mailjet 4.0.1 [3] * For Drupal 7.x, upgrade to Mailjet 7.x-2.23 [4] Reported By: * Drew Webber [5] of the Drupal Security Team Fixed By: * Drew Webber [6] of the Drupal Security Team * Bohdan Artemchuk [7] Coordinated By: * Drew Webber [8] of the Drupal Security Team [1] https://www.drupal.org/project/mailjet [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/mailjet/releases/4.0.1 [4] https://www.drupal.org/project/mailjet/releases/7.x-2.23 [5] https://www.drupal.org/user/255969 [6] https://www.drupal.org/user/255969 [7] https://www.drupal.org/user/289861 [8] https://www.drupal.org/user/255969

1 0

Node export - Moderately critical - Arbitrary PHP code execution - SA-CONTRIB-2024-061
by security-news＠drupal.org 20 Nov '24

20 Nov '24

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

1 0

Drupal core - Moderately critical - Cross Site Scripting - SA-CORE-2024-003
by security-news＠drupal.org 20 Nov '24

20 Nov '24

View online: https://www.drupal.org/sa-core-2024-003 Project: Drupal core [1] Date: 2024-November-20 Security risk: *Moderately critical* 13 ∕ 25 AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2] Vulnerability: Cross Site Scripting Affected versions: >= 8.8.0 < 10.2.11 || >= 10.3.0 < 10.3.9 || >= 11.0.0 < 11.0.8 Description: Drupal uses JavaScript to render status messages in some cases and configurations. In certain situations, the status messages are not adequately sanitized. 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] 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: * Jay Beaton [8] Fixed By: * Lee Rowlands [9] of the Drupal Security Team * catch [10] of the Drupal Security Team * Mingsong [11] * Juraj Nemec [12] of the Drupal Security Team * Dave Long [13] of the Drupal Security Team * Benji Fisher [14] of the Drupal Security Team Coordinated By: * Juraj Nemec [15] of the Drupal Security Team * Greg Knaddison [16] 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/352123 [9] https://www.drupal.org/user/395439 [10] https://www.drupal.org/user/35733 [11] https://www.drupal.org/user/2986445 [12] https://www.drupal.org/user/272316 [13] https://www.drupal.org/user/246492 [14] https://www.drupal.org/user/683300 [15] https://www.drupal.org/user/272316 [16] https://www.drupal.org/user/36762

1 0

Drupal core - Moderately critical - Access bypass - SA-CORE-2024-004
by security-news＠drupal.org 20 Nov '24

20 Nov '24

View online: https://www.drupal.org/sa-core-2024-004 Project: Drupal core [1] Date: 2024-November-20 Security risk: *Moderately critical* 10 ∕ 25 AC:Basic/A:User/CI:None/II:Some/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Affected versions: >= 8.0.0 < 10.2.11 || >= 10.3.0 < 10.3.9 || >= 11.0.0 < 11.0.8 Description: 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. 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.) Updating Drupal will not solve potential issues with existing accounts affected by this bug. See Fixing emails that vary only by case [8] for additional guidance. Reported By: * Wayne Eaker [9] Fixed By: * Wayne Eaker [10] * cilefen [11] of the Drupal Security Team * Kristiaan Van den Eynde [12] * Drew Webber [13] of the Drupal Security Team * Lee Rowlands [14] of the Drupal Security Team Coordinated By: * Juraj Nemec [15] of the Drupal Security Team * Benji Fisher [16] of the Drupal Security Team * xjm [17] 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/node/3486109 [9] https://www.drupal.org/user/326925 [10] https://www.drupal.org/user/326925 [11] https://www.drupal.org/user/1850070 [12] https://www.drupal.org/user/1345130 [13] https://www.drupal.org/user/255969 [14] https://www.drupal.org/user/395439 [15] https://www.drupal.org/user/272316 [16] https://www.drupal.org/user/683300 [17] https://www.drupal.org/u/xjm

1 0

Drupal core - Critical - Cross Site Scripting - SA-CORE-2024-005
by security-news＠drupal.org 20 Nov '24

20 Nov '24

View online: https://www.drupal.org/sa-core-2024-005 Project: Drupal core [1] Date: 2024-November-20 Security risk: *Critical* 17 ∕ 25 AC:None/A:None/CI:Some/II:Some/E:Theoretical/TD:Default [2] Vulnerability: Cross Site Scripting Description: Drupal 7 core's Overlay module doesn't safely handle user input, leading to reflected cross-site scripting under certain circumstances. Only sites with the Overlay module enabled are affected by this vulnerability. Solution: Install the latest version: * If you are using Drupal 7, update to Drupal 7.102 [3] * Sites may also disable the Overlay module to avoid the issue. Drupal 10 and Drupal 11 are not affected, as the Overlay module was removed from Drupal core in Drupal 8. Reported By: * Cesar [4] Fixed By: * Cesar [5] * Greg Knaddison [6] of the Drupal Security Team * Matthew Grill [7] * Wim Leers [8] * Drew Webber [9] of the Drupal Security Team * Ra Mänd [10] * Fabian Franz [11] * Juraj Nemec [12] of the Drupal Security Team Coordinated By: * Juraj Nemec [13] of the Drupal Security Team * Greg Knaddison [14] of the Drupal Security Team * xjm [15] 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/7.102 [4] https://www.drupal.org/user/3546810 [5] https://www.drupal.org/user/3546810 [6] https://www.drupal.org/user/36762 [7] https://www.drupal.org/user/1602706 [8] https://www.drupal.org/user/99777 [9] https://www.drupal.org/user/255969 [10] https://www.drupal.org/user/601534 [11] https://www.drupal.org/user/693738 [12] https://www.drupal.org/user/272316 [13] https://www.drupal.org/user/272316 [14] https://www.drupal.org/user/36762 [15] https://www.drupal.org/u/xjm

1 0

Drupal core - Less critical - Gadget chain - SA-CORE-2024-006
by security-news＠drupal.org 20 Nov '24

20 Nov '24

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

1 0

Drupal core - Moderately critical - Gadget chain - SA-CORE-2024-007
by security-news＠drupal.org 20 Nov '24

20 Nov '24

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

1 0

Drupal core - Moderately critical - Gadget chain - SA-CORE-2024-008
by security-news＠drupal.org 20 Nov '24

20 Nov '24

View online: https://www.drupal.org/sa-core-2024-008 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 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, 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. Solution: Install the latest version: * If you are using Drupal 7, update to Drupal 7.102 [3]. * If you are using Drupal 10.2, update to Drupal 10.2.11 [4]. * If you are using Drupal 10.3, update to Drupal 10.3.9 [5]. 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 * Fabian Franz [10] * Juraj Nemec [11] of the Drupal Security Team * Lee Rowlands [12] of the Drupal Security Team * Dave Long [13] of the Drupal Security Team * Alex Pott [14] of the Drupal Security Team Coordinated By: * Juraj Nemec [15] of the Drupal Security Team * Benji Fisher [16] of the Drupal Security Team * xjm [17] 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/7.102 [4] https://www.drupal.org/project/drupal/releases/10.2.11 [5] https://www.drupal.org/project/drupal/releases/10.3.9 [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/693738 [11] https://www.drupal.org/user/272316 [12] https://www.drupal.org/user/395439 [13] https://www.drupal.org/user/246492 [14] https://www.drupal.org/user/157725 [15] https://www.drupal.org/user/272316 [16] https://www.drupal.org/user/683300 [17] https://www.drupal.org/u/xjm

1 0