Biztonsági figyelmeztetések (contrib)

Project: Google TagDate: 2025-January-29Security risk: Moderately critical 12 ∕ 25 AC:Complex/A:None/CI:None/II:Some/E:Theoretical/TD:AllVulnerability: Cross Site Request ForgeryAffected versions: <1.8.0 || >=2.0.0 <2.0.8Description: 

This module enables you to integrate the site with the Google Tag Manager (GTM) application.

The module doesn't sufficiently validate the enabling or disabling of a tag container. The routes involved are not protected against Cross Site Request Forgery (CSRF).

This vulnerability is mitigated by the fact that an attacker needs to know the machine name of the container. The machine name is a random string, making an attack more difficult.

Solution: 

Install the latest version:

• If you use the Google Tag module 8.x, upgrade to Google Tag 8.x-1.8
• If you use the Google Tag module 2.0.x, upgrade to Google Tag 2.0.8

Reported By: 

• Pierre Rudloff
• Florent Torregrosa

Fixed By: 

• Jim Berry
• Jakob P

Coordinated By: 

• Greg Knaddison of the Drupal Security Team
• Juraj Nemec of the Drupal Security Team

Project: Google TagDate: 2025-January-29Security risk: Moderately critical 13 ∕ 25 AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:AllVulnerability: Cross Site ScriptingAffected versions: <1.8.0 || >=2.0.0 <2.0.8Description: 

This module enables you to integrate the site with the Google Tag Manager (GTM) application.

The module doesn't have the "restrict access" flag on the "administer google_tag_container" permission. A user with this permission can load a GTM container that completely changes the page or inserts malicious JS, resulting in a cross site scripting vulnerability.

This vulnerability is mitigated by the fact that an attacker must have a role with the aforementioned permission.

Solution: 

Install the latest version:

• If you use the Google Tag module 8.x, upgrade to Google Tag 8.x-1.8
• If you use the Google Tag module 2.0.x, upgrade to Google Tag 2.0.8

Reported By: 

• Pierre Rudloff

Fixed By: 

• Jakob P
• Jim Berry

Coordinated By: 

• Greg Knaddison of the Drupal Security Team
• Juraj Nemec of the Drupal Security Team

Project:  Drupal Admin LTE themeDate: 2025-January-29Security risk: Critical 16 ∕ 25 AC:Complex/A:Admin/CI:All/II:All/E:Theoretical/TD:AllVulnerability: UnsupportedAffected versions: *Description: 

The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...

Solution: 

If you use this project, you should uninstall it. To take over maintainership, please read https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...

Project: Authenticator LoginDate: 2025-January-29Security risk: Critical 18 ∕ 25 AC:Basic/A:None/CI:Some/II:All/E:Theoretical/TD:AllVulnerability: Access bypassAffected versions: <2.0.6Description: 

This module allows a site to setup two factor authentication via QR code using authenticator applications on mobile devices including phones.

The module does not properly protect its custom paths, allowing one user to access a different user's two factor configuration.

Solution: 

Install the latest version:

• If you use the alogin module 1.0.x, upgrade to at least Authenticator Login 2.0.6 or more recent, as the 1.0.x branch is now unsupported
• If you use the alogin module 2.0.x, upgrade to at least Authenticator Login 2.0.6 or more recent
• If you use the alogin module 2.1.x, you do not need to do anything

Reported By: 

• Ahmed Raza

Fixed By: 

• Ahmed Raza

Coordinated By: 

• Damien McKenna of the Drupal Security Team
• Ivo Van Geertruyen of the Drupal Security Team
• Juraj Nemec of the Drupal Security Team

Project: Matomo AnalyticsDate: 2025-January-29Security risk: Moderately critical 11 ∕ 25 AC:Complex/A:None/CI:None/II:Some/E:Theoretical/TD:DefaultVulnerability: Cross site request forgeryAffected versions: <1.24.0Description: 

This module enables you to add the Matomo web statistics tracking system to your website.

The Matomo Analytics Tag Manager sub-module allows you to add one or more Matomo tag containers on your website.

The module does not protect against Cross Site Request Forgeries on routes to enable or disable containers.

This vulnerability is mitigated by the fact that:

• The website needs to have the submodule "Matomo Analytics Tag Manager" enabled.
• An attacker must know the machine name of the container.

Solution: 

Install the latest version:

• If you use the Matomo Analytics module 8.x-1.23 and below, upgrade to Matomo Analytics 8.x-1.24

Reported By: 

• Ivo Van Geertruyen of the Drupal Security Team

Fixed By: 

• Ivo Van Geertruyen of the Drupal Security Team
• Florent Torregrosa

Coordinated By: 

• Ivo Van Geertruyen of the Drupal Security Team

Project: Ignition Error PagesDate: 2025-January-22Security risk: Critical 16 ∕ 25 AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:AllVulnerability: Cross Site ScriptingAffected versions: <1.0.4Description: 

This module enables you to render error pages using the Ignition package.

The module disables certain Drupal core code and does not perform sufficient filtering, allowing HTML to be injected in certain situations leading to a Cross Site Scripting (XSS) vulnerability.

This vulnerability is mitigated by the fact that this module is for development purposes and is not intended to be installed on production environments.

Solution: 

Install the latest version:

• If you use the Ignition Error Pages module for Drupal 10/11, upgrade to Ignition Error Pages 1.0.4

Reported By: 

• Dieter Holvoet

Fixed By: 

• catch of the Drupal Security Team
• Dieter Holvoet
• Heine Deelstra of the Drupal Security Team

Coordinated By: 

• Greg Knaddison of the Drupal Security Team
• Juraj Nemec of the Drupal Security Team
• James Gilliland of the Drupal Security Team

Project: Material AdminDate: 2025-January-22Security risk: Critical 16 ∕ 25 AC:Complex/A:Admin/CI:All/II:All/E:Theoretical/TD:AllVulnerability: UnsupportedAffected versions: *Description: 

The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...

Solution: 

If you use this project, you should uninstall it. To take over maintainership, please read https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...

Project: Flattern – Multipurpose Bootstrap Business ProfileDate: 2025-January-22Security risk: Critical 16 ∕ 25 AC:Complex/A:Admin/CI:All/II:All/E:Theoretical/TD:AllVulnerability: UnsupportedAffected versions: *Description: 

The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...

Solution: 

If you use this project, you should uninstall it. To take over maintainership, please read https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...

Project: AI (Artificial Intelligence)Date: 2025-January-22Security risk: Moderately critical 14 ∕ 25 AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:DefaultVulnerability: Access bypass, Information DisclosureAffected versions: <1.0.3Description: 

The AI logging sub-module enables you to log AI requests and responses for debugging and auditing purposes.

The module doesn't sufficiently check for access to view the preview listing of the logs. Full log details are correctly protected, and API keys are never logged.

This vulnerability is mitigated by the fact that it only affects sites using the AI Logging sub-module with 'Log requests' enabled in the AI Logging configuration page.

Solution: 

Install the latest version:

• If you use AI 1.x, upgrade to AI 1.0.3.

An update hook will update the view to use the view ai log permission. If you use version controlled configuration, remember to capture this.

(or) Disable the AI Logging module.

(or) Manually update the ai_logs view's access check to use the view ai log permission.

Reported By: 

• Mingsong

Fixed By: 

• Scott Euser
• Marcus Johansson
• Andrew Belcher

Coordinated By: 

• Greg Knaddison of the Drupal Security Team
• Juraj Nemec of the Drupal Security Team
• Dave Long of the Drupal Security Team

Project: AI (Artificial Intelligence)Date: 2025-January-15Security risk: Critical 15 ∕ 25 AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:DefaultVulnerability: Cross Site Request ForgeryAffected versions: >1.0.0 <1.0.2Description: 

The Drupal AI module provides a framework for easily integrating Artificial Intelligence on any Drupal site using any kind of AI (from multiple vendors). The sub-modules AI Chatbot and AI Assistants API allow users to interact with the Drupal site via a 'chat' interface.

The AI Chatbot module doesn't protect against Cross Site Request Forgeries in the Deepchat chatbot. This could allow an attacker to craft a scenario that can forge a request on behalf of a privileged user. When combined with the AI Search submodule, this could result in the AI Assistant exposing indexed data that the attacker should not have access to. When combined with the external AI Agent module, this could result in the AI Assistant exposing and allowing modification of site configuration of fields, content types, and vocabularies. Sites with custom built agents, with more privileged access, could be at greater risk from an exploit of this vulnerability.

This vulnerability is mitigated by:

• The targeted user needs to have an active session with a role with the "access deepchat api" permission and permission to assistants.
• To extract data, the target site must have a permissive CORS policy allowing the attacking site to read the result of a cross origin request.
• To modify data, the targeted user must have permission to use the configured agents.

Solution: 

Install the latest version:

• If you use the AI module, upgrade to AI 1.0.2

If you cannot update, you can can uninstall the AI Chatbot sub-module.

Reported By: 

• Marcus Johansson

Fixed By: 

• Marcus Johansson
• Michal Gow
• Kevin Quillen
• Andrew Belcher

Coordinated By: 

• Greg Knaddison of the Drupal Security Team
• Drew Webber of the Drupal Security Team
• Juraj Nemec of the Drupal Security Team

Project: Profile PrivateDate: 2025-January-08Security risk: Critical 15 ∕ 25 AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:AllVulnerability: UnsupportedAffected versions: *Description: 

The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...

Solution: 

If you use this project, you should uninstall it. To take over maintainership, please read https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...

Reported By: 

• Dezső Biczó

Coordinated By: 

• Ivo Van Geertruyen of the Drupal Security Team
• Cathy Theys of the Drupal Security Team
• Greg Knaddison of the Drupal Security Team

Project: Email TFADate: 2025-January-08Security risk: Moderately critical 14 ∕ 25 AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:AllVulnerability: Access bypassAffected versions: <2.0.3Description: 

This module enables you to do Two-Factor Authentication by email, using a user registered email to send a verification code to the user's email every time the user tries to log in to your site.

The module did not sufficiently protect against brute force attacks, allowing an attacker to bypass the second factor.

This vulnerability is mitigated by the fact the attacker must be able to present the username and first factor (i.e. password).

Solution: 

Install the latest version:

• If you use the Email TFA module, upgrade to Email TFA 2.0.3

Reported By: 

• Ursin Cola

Fixed By: 

• Ursin Cola
• abdulaziz zaid

Coordinated By: 

• Greg Knaddison of the Drupal Security Team
• Juraj Nemec of the Drupal Security Team

Project: Open SocialDate: 2024-December-11Security risk: Moderately critical 12 ∕ 25 AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:DefaultVulnerability: Access bypassAffected versions: <12.3.10 || >=12.4.0 <12.4.9Description: 

Open Social is a Drupal distribution for online communities, which ships with a default (optional) module social_file_private to ensure the images and files provided by the distribution are stored in the private instead of the public filesystem.

During updates from Open Social versions installed prior to 11.8.0 these files were not updated correctly and as a result the module didn't allow access checks to run correctly.

Solution: 

Install the latest version and make sure to run the update hooks.

• If you use Open Social 12.3.x upgrade to Open Social 12.3.10
• If you use Open Social 12.4.x upgrade to Open Social 12.4.9

Reported By: 

• corn696

Fixed By: 

• corn696
• Robert Ragas

Coordinated By: 

• Greg Knaddison of the Drupal Security Team

Project: Allow All File Extensions for file fieldsDate: 2024-December-11Security risk: Critical 18 ∕ 25 AC:Basic/A:User/CI:All/II:All/E:Theoretical/TD:AllVulnerability: UnsupportedAffected versions: *Description: 

The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...

Solution: 

If you use this project, you should uninstall it. To take over maintainership, please read https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...

Project: Git Utilities for DrupalDate: 2024-December-11Security risk: Critical 17 ∕ 25 AC:Basic/A:Admin/CI:All/II:All/E:Theoretical/TD:AllVulnerability: UnsupportedAffected versions: *Description: 

The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...

Solution: 

If you use this project, you should uninstall it. To take over maintainership, please read https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...

Project: Login DisableDate: 2024-December-11Security risk: Critical 16 ∕ 25 AC:None/A:User/CI:Some/II:Some/E:Theoretical/TD:AllVulnerability: Access bypassAffected versions: >=2.0.0 <2.1.1Description: 

This module enables you to prevent existing users from logging in to your Drupal site unless they know the secret key to add to the end of the ?q=user login form page.

The Login Disable module does not correctly prevent a user with a disabled login from logging in, allowing those users to by-pass the protection offered by the module.

This vulnerability is mitigated by the fact that an attacker must already have a user account to log in. This bug therefore allows users to log in even if their login is disabled.

Solution: 

Install the latest version:

• If you use the Login Disable module for Drupal 9.x / 10.x, upgrade to Login Disable 2.1.1

The Drupal 7 version of the module is not affected.

Reported By: 

• e5sego

Fixed By: 

• e5sego
• Sang Lostrie

Coordinated By: 

• Ivo Van Geertruyen of the Drupal Security Team
• Greg Knaddison of the Drupal Security Team
• Benji Fisher of the Drupal Security Team

Project: Browser Back ButtonDate: 2024-December-11Security risk: Moderately critical 13 ∕ 25 AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:AllVulnerability: Cross site scriptingAffected versions: >=1.0.0 <2.0.2Description: 

This module provides a block that renders a link providing the functionality of a browser's back button.

The module does not sufficiently escape text entered by an administrator, resulting in a cross scripting vulnerability.

This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer blocks".

Solution: 

Install the latest version:

• If you use the Browser Back Button module for Drupal 9.x/10.x, upgrade to Browser Back Button 2.0.2

Reported By: 

• Patrick Fey

Fixed By: 

• Elavarasan R

Coordinated By: 

• Ivo Van Geertruyen of the Drupal Security Team

Project: Entity Form StepsDate: 2024-December-04Security risk: Moderately critical 13 ∕ 25 AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:AllVulnerability: Cross site scriptingAffected versions: <1.1.4Description: 

This module allows a site builder to create multi-step entity forms leveraging the Field Group field type plugins.

The module doesn't escape plain text administrative configurations. An attacker with admin access could inject arbitrary JavaScript code.

This vulnerability is mitigated by the fact that an attacker must have a role with the 'administer [entity_type] form display' permission allowing access to configure entity form displays.

Solution: 

Install the latest version:

• If you use the Entity Form Steps module for Drupal 9.x/10.x, upgrade to Entity Form Steps 1.1.4

Reported By: 

• Ide Braakman

Fixed By: 

• Rob

Coordinated By: 

• Ivo Van Geertruyen of the Drupal Security Team

Project: Minify JSDate: 2024-December-04Security risk: Moderately critical 13 ∕ 25 AC:Basic/A:None/CI:None/II:Some/E:Theoretical/TD:AllVulnerability: Cross site request forgeryAffected versions: <3.0.3Description: 

The Minify JS module allows a site administrator to minify all javascript files that exist in the site's code base and use those minified files on the front end of the website.

Several administrator routes are unprotected against Cross-Site Request Forgery (CRSF) attacks.

Solution: 

Install the latest version:

• If you use the Minify JS module for Drupal 7.x, upgrade to Minify JS 7.x-1.11
• If you use the Minify JS module for Drupal 8.x, upgrade to Minify JS 3.0.3

Reported By: 

• Pierre Rudloff

Fixed By: 

• Ivo Van Geertruyen of the Drupal Security Team
• Scott Joudry

Coordinated By: 

• Ivo Van Geertruyen of the Drupal Security Team

Project: Download All FilesDate: 2024-December-04Security risk: Critical 16 ∕ 25 AC:None/A:None/CI:Some/II:None/E:Proof/TD:AllVulnerability: Access bypassAffected versions: <2.0.2Description: 

This module provides a field formatter for the field type 'file' called `Table of files with download all link` .

The module had vulnerabilities allowing a user to download files they normally should not be able to download.

Solution: 

Install the latest version:

• If you use the Download All Files module, upgrade to 2.0.2 version

Reported By: 

• Pierre Rudloff
• Jeroen Tubex

Fixed By: 

• Jeroen Tubex
• striknin
• Giuseppe

Coordinated By: 

• Greg Knaddison of the Drupal Security Team
• Damien McKenna of the Drupal Security Team
• Ivo Van Geertruyen of the Drupal Security Team