Feed aggregator

Custom Permissions - Moderately critical - Access bypass - SA-CONTRIB-2017-083

Project Security Advisories - Wed, 11/08/2017 - 12:22pm
Project: Custom PermissionsVersion: 8.x-1.x-devDate: 2017-November-08Security risk: Moderately critical 13∕25 AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:AllVulnerability: Access bypassDescription: 

Custom Permissions is a lightweight module that allows permissions to be created and managed through an administrative form.

When this module is in use, any user who is able to perform an action which rebuilds some of Drupal's caches can trigger a scenario in which certain pages protected by this module's custom permissions temporarily lose those custom access controls, thereby leading to an access bypass vulnerability.

Solution: 

Install the latest version:

Reported By: Fixed By: Coordinated By: 

Permissions by Term - Moderately critical - Access bypass - SA-CONTRIB-2017-082

Project Security Advisories - Wed, 11/08/2017 - 12:16pm
Project: Permissions by TermVersion: 8.x-1.x-devDate: 2017-November-08Security risk: Moderately critical 14∕25 AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:DefaultVulnerability: Access bypassDescription: 

The Permissions by Term module extends Drupal by adding functionality for restricting access to single nodes via taxonomy terms.

The module grants access to nodes that are being blocked by other node access modules and that the Permissions by Term module does not intend to control. Additionally, it grants access to unpublished nodes in node listings to users who should not be able to see them. These problems lead to an access bypass vulnerability.

This vulnerability is mitigated by the fact that it only occurs on sites that either have another node access module (besides Permissions by Term) in use, or that have node listings that are accessible to unprivileged users and that don't directly filter out unpublished content.

Solution: 

Install the latest version:

Reported By: Fixed By: Coordinated By: 

Automated Logout - Moderately critical - Cross Site Scripting - SA-CONTRIB-2017-081

Project Security Advisories - Wed, 11/01/2017 - 2:22pm
Project: Automated LogoutVersion: 7.x-4.x-devDate: 2017-November-01Security risk: Moderately critical 14∕25 AC:Basic/A:Admin/CI:Some/II:Some/E:Proof/TD:AllVulnerability: Cross Site ScriptingDescription: 

This module provides a site administrator the ability to log users out after a specified time of inactivity. It is highly customizable and includes "site policies" by role to enforce log out.

The module does not sufficiently filter user-supplied text that is stored in the configuration, resulting in a persistent Cross Site Scripting vulnerability (XSS).

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

Solution: 

Install the latest version:

Reported By: Fixed By: Coordinated By: 

Mosaik - Moderately critical - Cross-site scripting - SA-CONTRIB-2017-080

Project Security Advisories - Wed, 10/25/2017 - 12:28pm
Project: MosaikVersion: 7.x-1.x-devDate: 2017-October-25Security risk: Moderately critical 13∕25 AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:DefaultVulnerability: Cross-site scriptingDescription: 

The Mosaik module enables you to create pages or complex blocks in Drupal with the logic of a real mosaic and its pieces.

The module doesn't sufficiently sanitize the titles of fieldsets on its administration pages or the titles of blocks that it creates. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer mosaik".

Solution: 

Install the latest version:

Also see the Mosaik project page.

Reported By: Fixed By: Coordinated By: 

Brilliant Gallery - Highly critical - Multiple Vulnerabilities - SA-CONTRIB-2017-079

Project Security Advisories - Wed, 10/25/2017 - 12:09pm
Project: Brilliant GalleryVersion: 7.x-1.x-devDate: 2017-October-25Security risk: Highly critical 20∕25 AC:Basic/A:None/CI:All/II:All/E:Theoretical/TD:AllVulnerability: Multiple Vulnerabilities Description: 

This module enables you to display any number of galleries based on images located in the files folder.

The module doesn't sufficiently sanitize various database queries which may allow attackers to craft requests resulting in an SQL injection vulnerability. This vulnerability could be exploited even by anonymous users and could potentially allow them to take over the site.

The module doesn't sufficiently confirm a user's intent to save checklist data, which allows for a cross-site request forgery (CSRF) exploit to be executed by unprivileged users.

Some configuration fields are not filtered while rendered, resulting in a cross-site scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "Administer Brilliant Gallery".

Solution: 

Install the latest version:

Reported By: Fixed By: Coordinated By: 

Yandex.Metrics - Moderately critical - Cross site scripting - SA-CONTRIB-2017-78

Project Security Advisories - Wed, 10/18/2017 - 12:48pm
Project: Yandex.MetricsVersion: 7.x-3.x-dev7.x-2.x-dev7.x-1.x-devDate: 2017-October-18Security risk: Moderately critical 13∕25 AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:AllVulnerability: Cross site scriptingDescription: 

The Yandex.Metrics module allows you to look for key indicators of your site effectiveness.

The module doesn't sufficiently let users know a setting page should not be given to untrusted users.

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

Solution: 

Install the latest version:

  • If you use the Yandex.Metrics module for Drupal 7.x, upgrade to its 7.x-3.1

Also see the Yandex.Metrics project page.

Reported By: Fixed By: Coordinated By: 

netFORUM Authentication - Moderately critical - Access Bypass - SA-CONTRIB-2017-077

Project Security Advisories - Wed, 10/11/2017 - 1:01pm
Project: netFORUM AuthenticationVersion: 7.x-1.0Date: 2017-October-11Security risk: Moderately critical 12∕25 AC:None/A:None/CI:None/II:None/E:Theoretical/TD:AllVulnerability: Access BypassDescription: 

The netFORUM Authentication module implements external authentication for users against netFORUM.

The module does not correctly use flood control making it susceptible to brute force attacks.

Solution: 

Install the latest version:

Reported By: Coordinated By: Fixed By: 

Skype Status - Moderately Critical - Cross Site Scripting - DRUPAL-SA-CONTRIB-2017-076

Project Security Advisories - Wed, 09/20/2017 - 2:48pm
Description

This module enables you to obtain the status for a user's Skype account

The module doesn't sufficiently sanitize the user input for their Skype ID.

This vulnerability is mitigated by the fact that an attacker must have an account on the site and be allowed to edit/input their Skype ID.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Skype Status (skype_status) 7.x-1.x versions prior to 7.x-1.2.

Drupal core is not affected. If you do not use the contributed Skype Status module, there is nothing you need to do.

Solution

Install the latest version:

Also see the Skype Status project page.

Reported by Fixed by Coordinated by Contact and More Information

The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Drupal version: Drupal 7.x

Page Access - Unsupported - SA-CONTRIB-2017-75

Project Security Advisories - Wed, 09/20/2017 - 2:43pm
  • Advisory ID: DRUPAL-SA-CONTRIB-2017-75
  • Project: Page Access (third-party module)
  • Date: 20-September-2017
Description

This module will provide the option to give the View and Edit access for users and roles on each node pages.

The security team is marking this module unsupported. There is a known security issue with the module that has not been fixed by the maintainer. If you would like to maintain this module, please read: https://www.drupal.org/node/251466

Versions affected
  • All versions

Drupal core is not affected. If you do not use the contributed Page Access module, there is nothing you need to do.

Solution

If you use the Page Access module for Drupal you should uninstall it.

Also see the Page Access project page.

Reported by Fixed by

Not applicable

Contact and More Information

The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Flag clear - Moderately Critical - CSRF - DRUPAL-SA-CONTRIB-2017-074

Project Security Advisories - Wed, 09/13/2017 - 12:50pm
Description

The Flag clear module allows administrators to remove user flags for content. This functionality is often useful in user-submission use-cases, where users do not necessarily need to unflag things on their own.

The module doesn't sufficiently confirm a user's intent to take unflagging actions.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • All Flag clear module versions prior to 7.x-1.10.

Drupal core is not affected. If you do not use the contributed Flag clear module, there is nothing you need to do.

Solution

Install the latest version:

Also see the Flag clear project page.

Reported by Fixed by Coordinated by Contact and More Information

The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Drupal version: Drupal 7.x

CAPTCHA - Moderately Critical - Denial of Service - SA-CONTRIB-2017-073

Project Security Advisories - Wed, 09/06/2017 - 3:21pm
Description

This module enables you to use various techniques to block automated scripts / robots from submitting content to a site, e.g. to block spam comments.

The module doesn't properly store the session ID of visitors who are given a session which could lead to a Denial of Service attack.

This vulnerability is mitigated by the fact that Drupal does not give a session to all visitors, especially when used with advanced caching systems like Varnish.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • CAPTCHA 7.x-1.x versions prior to 7.x-1.5.

Drupal core is not affected. If you do not use the contributed CAPTCHA module, there is nothing you need to do.

Solution

Install the latest version:

Also see the CAPTCHA project page.

Reported by Fixed by Coordinated by Contact and More Information

The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Clientside Validation - Critical - Arbitary PHP Execution - DRUPAL-SA-CONTRIB-2017-072

Project Security Advisories - Wed, 09/06/2017 - 1:20pm
Description

The Clientside Validation module enables you to have clientside (Javascript) validation on your forms.

The module does not sufficiently validate parameters of a POST request made when validating a CAPTCHA.

For the 1.x version of this module, this vulnerability is mitigated by the fact that the CAPTCHA module must be enabled and the 'validate captcha' option of the Clientside Validation module must be enabled (this option is enabled by default).

For the 2.x version of this module, this vulnerability is mitigated by the fact that the CAPTCHA module must be enabled and the Clientside Validation captcha submodule must be enabled.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Clientside Validation 7.x-1.x versions prior to 7.x-1.44.
  • Clientside Validation 7.x-2.x versions prior to 7.x-2.0-beta1.

Drupal core is not affected. If you do not use the contributed Clientside Validation module, there is nothing you need to do.

Solution

Install the latest version:

Also see the Clientside Validation project page.

Reported by Fixed by Coordinated by Contact and More Information

The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Drupal version: Drupal 7.x

H5P - Critical - Reflected Cross Site Scripting (XSS) - DRUPAL-SA-CONTRIB-2017-071

Project Security Advisories - Wed, 08/30/2017 - 1:10pm
Description

The H5P module helps create interactive videos, question sets, drag and drop questions, multichoice questions, boardgames, presentations, flashcards and more using Drupal.

The module does not sufficiently filter text prior to printing it back to the page, leading to a Reflected Cross Site Scripting (XSS) vulnerability.

This vulnerability is mitigated by the fact that many modern browsers contain protection against some kinds of Reflected XSS vulnerabilities.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • H5P 7.x-1.x versions prior to 7.x-1.32.

Drupal core is not affected. If you do not use the contributed H5P- Create and Share Rich Content and Applications module, there is nothing you need to do.

Solution

Install the latest version:

  • If you use the H5P module for Drupal 7.x, upgrade to H5P 7.x-1.32

Also see the H5P- Create and Share Rich Content and Applications project page.

Reported by Fixed by Coordinated by Contact and More Information

The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Drupal version: Drupal 7.x

Commerce invoices - Highly Critical - SQL Injection and Cross Site scripting - DRUPAL-SA-CONTRIB-2017-070

Project Security Advisories - Wed, 08/30/2017 - 1:09pm
Description

Commerce Invoices allows you to enter an Invoice number, Company name and Amount and it will generate an Invoice that the client can pay on your site using any payment method supported by Drupal commerce.

SQL Injection

The module did not properly use Drupal's database API when querying the database with user supplied values, allowing an attacker to send a specially crafted request to modify the query or potentially perform additional queries.

The vulnerability is mitigated by the fact that the attacker must have the 'access checkout' permission - this permission is commonly granted.

Stored Cross Site Scripting (XSS)

The module did not filter user-supplied text prior to printing that text back to users of the site.

The vulnerability is mitigated by the fact that the attacker must have the 'access checkout' permission - this permission is commonly granted.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • All Commerce invoice versions prior to 7.x-1.1

Drupal core is not affected. If you do not use the contributed Commerce Invoices module, there is nothing you need to do.

Solution

Install the latest version:

Special note: the module's strings have changed. Any site that uses Drupal's localization system should review and update the translated strings on the site.

Also see the Commerce Invoices project page.

Reported by Fixed by Coordinated by Updates

A person above was marked as a member of the security team when they were not

Contact and More Information

The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Drupal version: Drupal 7.x

Update on Views Ajax vulnerability for Drupal 7 Views and Drupal 8 core. -- PSA-2017-002

Security Public Service Announcements - Wed, 08/16/2017 - 10:51pm
  • Advisory ID: DRUPAL-PSA-2017-002
  • Project: Drupal contributed modules
  • Version: 7.x, 8.x
  • Date: 2017-Aug-16
Description

The Drupal Security Team is now aware that the Views ajax access bypass vulnerability (DRUPAL-SA-CONTRIB-2017-068 and SA-CORE-2017-004) released 16 Aug 2017 is more severe than originally announced, because many widely used contrib modules don't have access restrictions set on the default views they provide. Any view that does not have access controls on the default (master) display may be vulnerable. The vulnerability does not require any authentication to be exploited. A successful exploit results in some non-public data being made public.

Sites running versions of Views prior to 7.x-3.17 or Drupal 8 core prior to version 8.3.7 (including Drupal 8.1.x and 8.2.x) should update immediately. Drupal 7 core is only affected if the Views module is enabled.

If you are unable to update Views, you can mitigate this by editing views that contain sensitive data in the Views UI and making sure they utilise one of the permission controls - such as 'require a role' or 'require a permission'. See Views permissions manual page for more information.

Contact and More Information

The Drupal Security Team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

Learn more about the Drupal Security Team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Drupal Core - Multiple Vulnerabilities - SA-CORE-2017-004

Core Security Advisories - Wed, 08/16/2017 - 12:38pm

Drupal 8.3.7 is a maintenance releases which contain fixes for security vulnerabilities.

Download Drupal 8.3.7

Updating your existing Drupal 8 sites is strongly recommended (see instructions for Drupal 8). This release fixes security issues only; there are no new features nor non-security-related bug fixes in this release. See the 8.3.7 release notes for details on important changes and known issues affecting this release. Read on for details of the security vulnerabilities that were fixed in this release.

Description Views - Access Bypass - Moderately Critical - Drupal 8 - CVE-2017-6923

When creating a view, you can optionally use Ajax to update the displayed data via filter parameters. The views subsystem/module did not restrict access to the Ajax endpoint to only views configured to use Ajax. This is mitigated if you have access restrictions on the view.

It is best practice to always include some form of access restrictions on all views, even if you are using another module to display them.

REST API can bypass comment approval - Access Bypass - Moderately Critical - Drupal 8 - CVE-2017-6924

When using the REST API, users without the correct permission can post comments via REST that are approved even if the user does not have permission to post approved comments.

This issue only affects sites that have the RESTful Web Services (rest) module enabled, the comment entity REST resource enabled, and where an attacker can access a user account on the site with permissions to post comments, or where anonymous users can post comments.

Entity access bypass for entities that do not have UUIDs or have protected revisions - Access Bypass - Critical - Drupal 8 - CVE-2017-6925

There is a vulnerability in the entity access system that could allow unwanted access to view, create, update, or delete entities. This only affects entities that do not use or do not have UUIDs, and entities that have different access restrictions on different revisions of the same entity.

Versions affected
  • Drupal core 8.x versions prior to 8.3.7
Solution

Install the latest version:

Drupal 7 core is not affected, however, Drupal 7 Views is: see Views - Moderately Critical - Access Bypass - DRUPAL-SA-CONTRIB-2017-068

Also see the Drupal core project page.

Reported by Views - Access Bypass REST API can bypass comment approval - Access Bypass Entity access bypass for entities that do not have UUIDs or protected revisions - Access Bypass Fixed by Views - Access Bypass REST API can bypass comment approval - Access Bypass Entity access bypass for entities that do not have UUIDs or protected revisions - Access Bypass Contact and More Information

The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Views refresh - Moderately Critical - Access Bypass - DRUPAL-SA-CONTRIB-2017-069

Project Security Advisories - Wed, 08/16/2017 - 12:02pm
Description

When creating a view, you can optionally use Ajax to update the displayed data via filter parameters. The views refresh module did not restrict access to the Ajax endpoint to only views configured to use Ajax. This is mitigated if you have access restrictions on the view.

It is best practice to always include some form of access restrictions on all views, even if you are using another module to display them.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • views fresh versions prior to 7.x-1.2.

Drupal core is not affected. If you do not use the contributed Views refresh module, there is nothing you need to do.

Solution

Install the latest version:

Also see the Views refresh project page.

Reported by Fixed by Coordinated by Contact and More Information

The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Views - Moderately Critical - Access Bypass - DRUPAL-SA-CONTRIB-2017-068

Project Security Advisories - Wed, 08/16/2017 - 11:56am
Description

When creating a view, you can optionally use Ajax to update the displayed data via filter parameters. The views subsystem/module did not restrict access to the Ajax endpoint to only views configured to use Ajax. This is mitigated if you have access restrictions on the view.

It is best practice to always include some form of access restrictions on all views, even if you are using another module to display them.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Views versions prior to 7.x-3.17.

Drupal core is not affected. If you do not use the contributed Views module, there is nothing you need to do.

Solution

Install the latest version:

  • If you use the Views module for Drupal 7.x, upgrade to views 7.x-3.17

Also see the Views project page.

Reported by Fixed by Coordinated by Contact and More Information

The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Entity Reference - Moderately Critical - Access Bypass - DRUPAL-SA-CONTRIB-2017-067

Project Security Advisories - Wed, 08/16/2017 - 11:35am
Description

The entity reference module provides a field type that can reference arbitrary entities.

In a vulnerable configuration, an attacker could determine the titles of nodes they do not have access to.

This is mitigated as only entity reference fields using the "simple" entity selector are vulnerable, and the attack is not possible if any access control (i.e. node access) is in place (the attacker's role is missing only the "access content" permission to be able to view the content.)

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • entityreference 7.x-1.x versions prior to 7.x-1.5.

Drupal core is not affected. If you do not use the contributed Entity reference module, there is nothing you need to do.

Solution

Install the latest version:

Also see the Entity reference project page.

Reported by Fixed by Coordinated by Contact and More Information

The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Facebook Like Button - Moderately Critical - XSS - DRUPAL-SA-CONTRIB-2017-066

Project Security Advisories - Wed, 08/09/2017 - 10:53am
Description

This module provides a Facebook Like button on node pages and blocks.
The module does not sufficiently sanitize output when configured to use custom css rules.
This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer fblikebutton".

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Facebook Like Button 7.x-2.x versions prior to 7.x-2.6.

Drupal core is not affected. If you do not use the contributed Facebook Like Button module, there is nothing you need to do.

Solution

Install the latest version:

Also see the Facebook Like Button project page.

Reported by Fixed by Coordinated by Contact and More Information

The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Pages