Hírolvasó

Project: Booking and Availability Management Tools for DrupalDate: 2019-October-16Security risk: Moderately critical 11∕25 AC:Basic/A:User/CI:Some/II:None/E:Theoretical/TD:AllVulnerability: Access BypassDescription: 

The Bat module provides a foundation through which a wide range of availability management, reservation and booking use cases can be addressed.

The routes used to view events don't sufficiently guard access for non-privileged users. Specifically, a user with the 'View own' permission for bat events can view others' events as well.

Solution: 

Install the latest version:

• If you use the bat module for Drupal 8.x, upgrade to bat 8.x-1.2

Also see the Booking and Availability Management Tools for Drupal project page.

Reported By: 

• Jelle Sebreghts

Fixed By: 

• Adrian Rollett
• Lee Rowlands of the Drupal Security Team
• Jelle Sebreghts

Coordinated By: 

• Greg Knaddison of the Drupal Security Team

Project: MaxlengthDate: 2019-October-09Security risk: Moderately critical 13∕25 AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:AllVulnerability: Cross Site ScriptingDescription: 

This module enables you to set a maximum length allowed on text fields and indicate how many characters are left.

The module doesn't sufficiently filter strings leading to a Cross Site Scripting (XSS) vulnerability.

This vulnerability is mitigated by the fact the malicious script will not be triggered in the browser of UID 1 nor any user with "Bypass maxlength setting".

Solution: 

Install the latest version:

• If you use the Maxlength module for Drupal 7.x, upgrade to Maxlength 7.x-3.3

Also see the Maxlength project page.

Reported By: 

• Yonatan Offek

Fixed By: 

• Yonatan Offek
• Aron Novak
• Daniel Wehner

Coordinated By: 

• Greg Knaddison Drupal Security Team member

Project: Localization updateDate: 2019-October-02Security risk: Moderately critical 10∕25 AC:Complex/A:Admin/CI:Some/II:Some/E:Theoretical/TD:UncommonVulnerability: Insecure server configurationDescription: 

This module enables you to automatically download and update the site's interface translation by fetching them from localize.drupal.org or any other Localization server.

The module doesn't sufficiently protect the directory it stores translation files in. It's conventional for directories which may be writeable to be protected by a .htaccess file to prevent malicious PHP files placed within them being executed by the webserver. This vulnerability is mitigated by the fact that an attacker typically wouldn't be able to place a malicious file in the module's storage directory.

Solution: 

Install the latest version:

• If you use the Localization Update module for Drupal 7.x-1.x, upgrade to Localization Update 7.x-1.2
• If you use the Localization Update module for Drupal 7.x-2.x, upgrade to Localization Update 7.x-2.3

Also see the Localization update project page.

Reported By: 

Gisle Hannemyr

Fixed By: 

• Gisle Hannemyr
• Erik Stielstra
• Gábor Hojtsy

Coordinated By: 

• Damien McKenna of the Drupal Security Team

Project: Simple AMP (Accelerated Mobile Pages)Date: 2019-October-02Security risk: Moderately critical 13∕25 AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:AllVulnerability: Access bypassDescription: 

This module allows display of a site's content in AMP format.

The module doesn't sufficiently check access on unpublished or restricted content.

Solution: 

Install the latest version of the module.

• If you use the Simple AMP module for Drupal 8.x, upgrade to Simple AMP 8.x-1.16

Also see the Simple AMP (Accelerated Mobile Pages) project page.

Reported By: 

• M. H.

Fixed By: 

• Minnur Yunusov
• M. H.

Coordinated By: 

• Damien McKenna of the Drupal Security Team

Project: UbercartDate: 2019-October-02Security risk: Moderately critical 11∕25 AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:UncommonVulnerability: Cross site scriptingDescription: 

The Ubercart module provides a shopping cart and e-commerce features for Drupal.

The order module doesn't sufficiently sanitize user input when displayed on an invoice leading to a Cross Site Scripting (XSS) vulnerability.

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

Solution: 

Install the latest version:

• If you use the Ubercart module for Drupal 7.x, upgrade to Ubercart 7.x-3.13

Also see the Ubercart project page.

Reported By: 

• Devin Zuczek

Fixed By: 

• Devin Zuczek
• Dave Long

Coordinated By: 

• Greg Knaddison of the Drupal Security Team

Project: GutenbergDate: 2019-September-25Security risk: Critical 16∕25 AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:AllVulnerability: Access bypassDescription: 

This module provides a new UI experience for node editing - Gutenberg editor.

The routes used by the Gutenberg editor lack proper permissions allowing untrusted users to view and modify some content they should not be able to view or modify.

Solution: 

Install the latest version:

• If you use the Gutenberg module 8.x-1.x, upgrade to 8.x-1.8
• For roles other than administrator, the Administer Gutenberg permission must be given to handle media files on the Gutenberg editor.

Also see the Gutenberg project page.

Reported By: 

• Marco Fernandes
• Greg Knaddison of the Drupal Security Team

Fixed By: 

• Marco Fernandes
• Thor Andre Gretland
• Mariusz Andrzejewski

Coordinated By: 

• Greg Knaddison of the Drupal Security Team

Project: Permissions by TermVersion: 8.x-1.x-devDate: 2019-September-25Security risk: Moderately critical 14∕25 AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:DefaultVulnerability: Access bypassDescription: 

This module enables you to control access to content based on taxonomy terms. The module doesn't sufficiently check if a given entity should be access controlled, defaulting to allowing access even to unpublished nodes.

The vulnerability is mitigated by the fact that the submodule Permissions by Entity must also be enabled.

Solution: 

Install the latest version:

• If you use the Permissions by Term module for Drupal 8.x, upgrade to Permissions by Term 8.x-2.11

Also see the Permissions by Term project page.

Reported By: 

• Jimmy Henderickx

Fixed By: 

• Marc-Oliver Teschke

Coordinated By: 

• Heine of the Drupal Security Team
• Ivo Van Geertruyen of the Drupal Security Team

Project: TableFieldVersion: 8.x-2.x-devDate: 2019-September-18Security risk: Moderately critical 12∕25 AC:None/A:User/CI:Some/II:None/E:Theoretical/TD:DefaultVulnerability: Access bypassDescription: 

This module allows you to attach tabular data to an entity.

There is insufficient access checking for users with the ability to "Export Tablefield Data as CSV". They can export data from unpublished nodes or otherwise inaccessible entities.

This vulnerability is mitigated by the fact that an attacker must have a role with the permission "Export Tablefield Data as CSV".

Solution: 

Install the latest version:

• If you use the Tablefield module for Drupal 8.x, upgrade to Tablefield 8.x-2.1

Also see the TableField project page.

Reported By: 

• Mitch Portier

Fixed By: 

• Mitch Portier
• Jen Lampton
• Martin Postma

Coordinated By: 

• Chris McCafferty of the Drupal Security Team
• Greg Knaddison of the Drupal Security Team
• Drew Webber of the Drupal Security Team

Project: Create user permissionVersion: 8.x-1.x-devDate: 2019-September-18Security risk: Critical 15∕25 AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:DefaultVulnerability: Access bypassDescription: 

This module enables you to have a separate permission only for creating users.

The module doesn't respect Drupal's setting for "Who can register accounts?" when set to "Visitors, but administrator approval is required".

When this option is chosen, the module overrides the setting, and makes it possible to register accounts with no approval.

This vulnerability can be mitigated by having other settings in place for account registration, such as requiring email verification for new accounts, or permitting account creation for "Administrators only".

Solution: 

Install the latest version:

• If you use the create_user_permission module for Drupal 8.x, upgrade to Create user permission 8.x-1.2

Also see the Create user permission project page.

Reported By: 

• jddh

Fixed By: 

• Eirik Morland

Coordinated By: 

• Michael Hess of the Drupal Security Team
• Greg Knaddison of the Drupal Security Team
• Drew Webber of the Drupal Security Team

Project: Imagecache ExternalDate: 2019-August-21Security risk: Critical 15∕25 AC:Complex/A:None/CI:Some/II:Some/E:Theoretical/TD:AllVulnerability: Insecure session token managementDescription: 

This module that allows you to store external images on your server and apply your own Image Styles.

The module exposes cookies to external sites when making external image requests.

This vulnerability is mitigated by using the whitelisted host feature to restrict external image requests from trusted sources.

Solution: 

Install the latest version:

• If you use the Imagecache External 8.x-1.0 version, upgrade to Imagecache External 8.x-1.1 version

Also see the Imagecache External project page.

Reported By: 

• Jason Want
• Heine Deelstra of the Drupal Security Team

Fixed By: 

• Heine Deelstra of the Drupal Security Team
• Baris Wanschers

Coordinated By: 

• Greg Knaddison of the Drupal Security Team

Project: Forms StepsDate: 2019-August-14Security risk: Critical 16∕25 AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:AllVulnerability: Access bypassDescription: 

Forms Steps provides an UI to create form workflows using form modes. It creates quick and configurable multisteps forms.

The module doesn't sufficiently check user permissions to access its workflows entities that allows to see any entities that have been created through the different steps of its multistep forms.

This vulnerability is mitigated by the fact that you have to know the Forms Steps URL to create a content linked to the flow. Also, all created content is very hard to edit through the same flow as you have to know the URL and the linked hash to the content.

Solution: 

Install the latest version:

• If you use the Forms Steps module for Drupal 8.x, upgrade to Forms Steps 8.x-1.2

Also see the Forms Steps project page.

Reported By: 

• solide-echt

Fixed By: 

• Hakim Rachidi
• solide-echt
• nicoloye

Coordinated By: 

• Michael Hess of the Drupal Security Team
• Greg Knaddison of the Drupal Security Team

Project: External Links FilterDate: 2019-August-14Security risk: Moderately critical 10∕25 AC:Basic/A:None/CI:None/II:None/E:Theoretical/TD:AllVulnerability: Open Redirect VulnerabilityDescription: 

The External Link Filter module provides an input filter that replaces external links by a local link that redirects to the target URL.

The module did not have protection for the Redirect URL to go where content authors intended.

Solution: 

Install the latest version:

• If you use the External Links Filter module for Drupal 7.x, upgrade to External Links Filter version 7.x-3.1
• If you use the External Links Filter module for Drupal 8.x, upgrade to External Links Filter version 8.x-1.2

Also see the External Links Filter project page.

Reported By: 

• Manuel Adán

Fixed By: 

• Manuel Adán
• Dmitry Drozdik

Coordinated By: 

• Michael Hess of the Drupal Security Team
• Greg Knaddison of the Drupal Security Team

Project: Super LoginDate: 2019-August-14Security risk: Moderately critical 13∕25 AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:AllVulnerability: Cross site scriptingDescription: 

This module improves the Drupal login page with the new features and layout.

The module doesn't sufficiently filter input text in the administration pages text configuration inputs. For example, the login text field.

The vulnerability is mitigated by the fact it can only be exploited by a user with the "Administer super login" permission.

Solution: 

Install the latest version:

• If you use the Super Login module for Drupal 8.x, upgrade to Super Login 8.x-1.3
• If you use the Super Login module for Drupal 7.x, upgrade to Super Login 7.x-1.4

Also see the Super Login project page.

Reported By: 

• Mitch Portier

Fixed By: 

• Mitch Portier
• Shawn Ostermann

Coordinated By: 

• Greg Knaddison of the Drupal Security Team

Project: scroll to topDate: 2019-August-14Security risk: Moderately critical 13∕25 AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:AllVulnerability: Cross site scriptingDescription: 

The Scroll To Top module enables you to have an animated scroll to top link in the bottom of the node.

The module does not sufficiently filter configuration text leading to a Cross Site Scripting (XSS) vulnerability.

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

Solution: 

Install the latest version of the module.

• If you use the Scroll To Top module for Drupal 7.x, upgrade to Scroll To Top 7.x-2.2

Also see the scroll to top project page.

Reported By: 

• Ayesh Karunaratne
• Yonatan Offek

Fixed By: 

• Ayesh Karunaratne
• Tarek Djebali

Coordinated By: 

• Michael Hess of the Drupal Security Team
• Greg Knaddison of the Drupal Security Team

Project: Existing Values Autocomplete WidgetDate: 2019-July-24Security risk: Critical 17∕25 AC:None/A:None/CI:All/II:None/E:Theoretical/TD:AllVulnerability: Access bypassDescription: 

This module provides an autocomplete widget for text fields that suggests all existing (previously entered) values for that field.

The module doesn't sufficiently check for proper access permission before returning autocomplete results.

This vulnerability is mitigated by the fact that an attacker must know the route to the autocomplete callback controller though this is easily known.

Solution: 

Install the latest version:

• If you use the Existing Values Autocomplete Widget module for Drupal 8.x, upgrade to Existing Values Autocomplete Widget 8.x-1.2

Also see the Existing Values Autocomplete Widget project page.

Reported By: 

• David Stinemetze

Fixed By: 

• Art Williams

Coordinated By: 

• Michael Hess of the Drupal Security Team
• Greg Knaddison of the Drupal Security Team

Project: Facebook Messenger Customer Chat PluginDate: 2019-July-24Security risk: Critical 16∕25 AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:AllVulnerability: Access bypassDescription: 

The Facebook Messenger Customer Chat Plugin module enables you to add the Facebook Messenger Customer Chat Plugin to your Drupal site.

The module doesn't require user permissions on the admin page.

Solution: 

Install the latest version:

• If you use the Facebook Messenger Customer Chat Plugin module for Drupal 7.x, upgrade to Facebook Messenger Customer Chat Plugin 7.x-1.1

Also see the Facebook Messenger Customer Chat Plugin project page.

Reported By: Reported by

• Marcelo Vani

Fixed By: 

• Marcelo Vani

Coordinated By: 

• Michael Hess of the Drupal Security Team
• Greg Knaddison of the Drupal Security Team

Project: MetatagDate: 2019-July-24Security risk: Moderately critical 13∕25 AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:UncommonVulnerability: Information disclosureDescription: 

This module enables you to customize meta tags to help with a site's search engine ranking and improve the display of page summaries when shared on social networks.

The module doesn't sufficiently check for a site being in maintenance mode.

This vulnerability is mitigated by the fact that the site must be configured to disallow access to certain content, and must be put into maintenance mode.

Solution: 

Install the latest version:

• If you use the Metatag module for Drupal 8.x, upgrade to Metatag 8.x-1.9

Also see the Metatag project page.

Reported By: 

• Shloma

Fixed By: 

• Damien McKenna of the Drupal Security Team

Coordinated By: 

• Damien McKenna of the Drupal Security Team

Project: Drupal coreDate: 2019-July-17Security risk: Critical 17∕25 AC:None/A:None/CI:Some/II:Some/E:Theoretical/TD:DefaultVulnerability: Access bypassCVE IDs: CVE-2019-6342Description: 

In Drupal 8.7.4, when the experimental Workspaces module is enabled, an access bypass condition is created.

This can be mitigated by disabling the Workspaces module. It does not affect any release other than Drupal 8.7.4.

Drupal 8.7.3 and earlier, Drupal 8.6.x and earlier, and Drupal 7.x are not affected.

Solution: 

If the site is running Drupal 8.7.4, upgrade to Drupal 8.7.5.

Note, manual step needed. For sites with the Workspaces module enabled, update.php needs to run to ensure a required cache clear. If there is a reverse proxy cache or content delivery network (e.g. Varnish, CloudFlare) it is also advisable to clear these as well.

Reported By: 

• Dave Botsch

Fixed By: 

• Michael Hess of the Drupal Security Team
• Jess of the Drupal Security Team
• Greg Knaddison of the Drupal Security Team
• Chris McCafferty of the Drupal Security Team
• Neil Drumm of the Drupal Security Team
• Alex Pott of the Drupal Security Team
• Andrei Mateescu

Project: Meta tags quickDate: 2019-July-17Security risk: Moderately critical 13∕25 AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:AllVulnerability: Cross Site ScriptingDescription: 

Metatags quick is a module that manages meta tags (tags that appear in HTML's head section) as Drupal 7 fields.
Administration page of metatags quick does not sanitize the output of blocks that appear on the same page. This allows an attacker to inject malicious JavaScript in block markup.
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 Metatags quick module for Drupal 7.x, upgrade to metatags quick 7.x-2.10.

Reported By: 

• Yonatan Offek

Fixed By: 

• Valery Lourie
• Yonatan Offek

Coordinated By: 

• Greg Knaddison of the Drupal Security Team

Project: ImageCache ActionsDate: 2019-July-17Security risk: Critical 17∕25 AC:Basic/A:Admin/CI:All/II:All/E:Theoretical/TD:AllVulnerability: Multiple Vulnerabilities Description: 

The imagecache actions module defines a number of additional image effects that can be used to create image styles. The "Image styles admin" sub module provides additional functionality to duplicate, export and import image styles. The module uses unserialize() to import image styles into another site where unserialize() is known to have security issues when processing potentially unsafe input.

This vulnerability is mitigated by the fact that the "Image styles admin" sub module must be enabled and an attacker must have a role with the permission "'administer image styles'".

Furthermore, the import functionality supports PHP code included in image effects as part of an image style, which would run on image derivative generation subject to the PHP module being enabled. This is intended behaviour for the "Image styles admin" sub module, but the user access restrictions should reflect the potential risks involved.

The new security release of this module introduces a new "import image styles" permission which is marked as restricted. In order to use the image style import functionality, users will need to have a role which has this new permission in addition to "administer image styles" (which is not marked as restricted).

Solution: 

• If you use the Imagecache Actions module for Drupal 7.x, upgrade to Imagecache Actions 7.x-1.10.
• Image Effects, the D8 successor is *not* vulnerable to this exploit.

Reported By: 

• Ruben Hofman

Fixed By: 

• Erwin Derksen
• Greg Knaddison of the Drupal Security Team

Coordinated By: 

• Greg Knaddison of the Drupal Security Team
• Ivo Van Geertruyen of the Drupal Security Team
• Drew Webber of the Drupal Security Team