Drupal contrib security advisories

Project: Drupal OAuth Server ( OAuth Provider) - Single Sign On ( SSO )Date: 2020-October-14Security risk: Moderately critical 12∕25 AC:Basic/A:None/CI:None/II:Some/E:Theoretical/TD:DefaultVulnerability: SQL InjectionDescription: 

This module enables you login into any OAuth 2.0 compliant application using Drupal credentials.

The 8.x branch of the module is vulnerable to SQL injection.

Solution: 

Install the latest version:

• If you use the Drupal OAuth Server module for Drupal 8.x, upgrade to 8.x-1.1

Reported By: 

• Jakub Piasecki

Fixed By: 

• Gaurav Sood
• Greg Knaddison of the Drupal Security Team
• Samuel Mortenson of the Drupal Security Team

Coordinated By: 

• Michael Hess of the Drupal Security Team

Project: GroupVersion: 8.x-1.x-devDate: 2020-August-05Security risk: Moderately critical 11∕25 AC:None/A:User/CI:Some/II:None/E:Theoretical/TD:UncommonVulnerability: Information disclosureDescription: 

The Group module enables you to hand out permissions on a smaller subset, section or community of your website.

Under very specific circumstances, where two group types support the same content, yet hand out different permissions, non-members of the first group type may use the set of permissions of the 2nd group type for the grouped content.

This vulnerability is mitigated by the fact that you must already have a rare set-up and the two group types are configured in a way where one is more permissive than the other over the same type of content.

Solution: 

Install the latest version:

• If you are using 8.x-1.0 or later, you should upgrade to 8.x-1.2.
• If you are using 8.x-1.0-rc5, that version is not affected by this issue. You can also consider upgrading to 8.x-1.2.

Reported By: 

• John Pitcairn

Fixed By: 

• Kristiaan Van den Eynde

Project: GroupVersion: 8.x-1.x-devDate: 2020-August-05Security risk: Moderately critical 12∕25 AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:DefaultVulnerability: Information disclosureDescription: 

The Group module enables you to hand out permissions on a smaller subset, section or community of your website.

With the 1.1 security release, new code was introduced to ensure proper access for all entity types, but a mistake introduced unexpected access to unpublished nodes.

Solution: 

Install the latest version:

• If you are using 8.x-1.0 or later, you should upgrade to 8.x-1.2.
• If you are using 8.x-1.0-rc5, that version is not affected by this issue. You can also consider upgrading to 8.x-1.2.

Reported By: 

• Sean Blommaert
• Martijn Vermeulen

Fixed By: 

• Kristiaan Van den Eynde

Project: Hostmaster (Aegir)Version: 7.x-3.x-devDate: 2020-July-29Security risk: Moderately critical 14∕25 AC:Complex/A:Admin/CI:All/II:All/E:Theoretical/TD:UncommonVulnerability: Access bypass, Arbitrary code executionDescription: 

Aegir is a powerful hosting system that sits alongside a LAMP or LEMP server to create, deploy and manage Drupal sites.

Given that

• Aegir can use both Apache and Nginx Web servers,
• Apache allows configuration-writing users to escalate their privileges to the superuser root, and
• Aegir's operations are performed by the GNU/Linux user aegir,

It follows that:

• Users with access to the aegir account can escalate their privileges to root.
• Any PHP code submitted through the front-end Web UI via enabling modules (such as PHP, Views PHP, and Computed Field) could be run as root though a cron hook implementation. (Aegir runs cron through the aegir user via Drush.)

This vulnerability is mitigated by the fact that

• an attacker must have access to the aegir account, and
• the Web server must be Apache.

While it was generally assumed that aegir access should only be provided to trusted users (i.e. users who also have access to root), this wasn't explicitly stated. The documentation has since been updated.

Solution: 

If you're running Aegir and have granted untrusted users access to the aegir account,

1. revoke aegir account access for users who you would not trust with root access,
2. disable any module functionality on the hosted Drupal sites that allows PHP code to be entered on the front-end Web UI. Computed Field, for example, can still be used safely by providing code from the back-end only. (See Stop allowing PHP from being entered on the Web UI for a plan to enforce this.)

We do not recommend switching to an Nginx Web server instead of revoking access. This is because there could be as-yet-unknown privilege-escalation exploits involving Nginx (as with any other piece of software).

Switching to Nginx

While not recommended, if this is something you'd like to do in addition to making the above change, we can offer some information on how to do it.

While there may eventually be a migration path to convert existing Apache installations to Nginx, the recommended approach is currently:

1. Set up a new Aegir installation using Nginx.
2. Remotely import sites from the original Apache server.
3. Decommission the original Apache server.

Also see the Hostmaster (Aegir) project page.

Reported By: 

• Noam Rathaus

Fixed By: 

• Colan Schwartz

Coordinated By: 

• Heineof the Drupal Security Team
• Greg Knaddisonof the Drupal Security Team

Project: GroupVersion: 8.x-1.x-devDate: 2020-July-29Security risk: Critical 15∕25 AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:AllVulnerability: Information DisclosureDescription: 

This module enables you to hand out permissions on a smaller subset, section or community of your website.

The module used to leverage the node grants system but turned it off in its recent 8.x-1.0 release in favor of a system that works for ALL entity types, not just nodes. By doing so, some regular node access checks turned from neutral into allowed because of the way the node grants system operates.

This vulnerability is mitigated by the fact that an attacker must have the GroupNode plugin installed on their website and have no other hook_node_grants() implementations on their website aside from the one that was recently removed by Group. If you do not use the GroupNode plugin or still have hook_node_grants() implementing modules enabled, your site may not be affected.

Solution: 

Install the latest version:

• If you are using 8.x-1.0-rc5 you can keep using that version or upgrade to 8.x-1.1
• If you are using 8.x-1.0 you should upgrade to 8.x-1.1

Reported By: 

• Kristiaan Van den Eynde

Fixed By: 

• Kristiaan Van den Eynde

Coordinated By: 

• Greg Knaddison Of the Drupal Security Team

Project: Modal FormVersion: 8.x-1.x-devDate: 2020-July-22Security risk: Critical 16∕25 AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:AllVulnerability: Access bypassDescription: 

The Modal form module is a toolset for quick start of using forms in modal windows.

Any form is available for view and submit when the modal_form module is installed. The only requirement is to know the form's fully-qualified class name.

Solution: 

Upgrade to modal_form-8.x-1.2.

Also see the Modal Form project page.

Reported By: 

• Dave Long

Fixed By: 

• Sergii Bondarenko

Coordinated By: 

• Greg Knaddison of the Drupal Security Team

Project: Apigee EdgeVersion: 8.x-1.x-devDate: 2020-July-22Security risk: Moderately critical 10∕25 AC:Basic/A:User/CI:Some/II:None/E:Theoretical/TD:DefaultVulnerability: Access bypassDescription: 

The Apigee Edge module allows connecting a Drupal site to Apigee Edge in order to build a developer portal. It contains an "Apigee Edge Teams" submodule that provides shared app functionality by allowing developers to be organized into teams.

The "Apigee Edge Teams" submodule has an information disclosure vulnerability. The "Add team member" form displays an email autocomplete field which can expose the email addresses of other accounts in the system.

This vulnerability is mitigated by the fact that to have access to the form, the site must have the Apigee Edge Teams submodule enabled, and the user must have a team role that has the "Manage team members" permission. (Note that team roles and permissions are not related to Drupal core roles and permissions).

Solution: 

Install the latest version:

• If you use the apigee_edge_teams submodule for Drupal 8.x, upgrade to Apigee Edge module 8.x-1.12

Also see the Apigee Edge project page.

Reported By: 

• Arlina Espinoza Rhoton

Fixed By: 

• Arlina Espinoza Rhoton
• Chris Novak

Coordinated By: 

• Greg Knaddison of the Drupal Security Team

Project: Easy BreadcrumbVersion: 8.x-1.x-devDate: 2020-July-22Security 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 use the current URL (path alias) and the current page's title to automatically extract the breadcrumb's segments and its respective links then show them as breadcrumbs on your website.

The module doesn't sufficiently sanitize editor input in certain circumstances leading to a Cross Site Scripting (XSS) vulnerability.

This vulnerability requires the user have 'administer Easy Breadcrumb settings permission'.

Solution: 

Install the latest version:

• If you use the Easy Breadcrumb module for Drupal 8, upgrade to Easy Breadcrumb 8.x-1.13

Also see the Easy Breadcrumb project page.

Reported By: 

• Greg Boggs

Fixed By: 

• Greg Boggs
• Samuel Mortenson of the Drupal Security Team

Coordinated By: 

• Greg Knaddison of the Drupal Security Team