Project Security Advisories

Subscribe to Project Security Advisories feed
Updated: 1 hour 19 min ago

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

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

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

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

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

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

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

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

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

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

Session Cache API - Critical - Multiple vulnerabilities - DRUPAL-SA-CONTRIB-2017-065

Wed, 08/09/2017 - 10:04am
Description

This module does not safely deal with serialization.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Session Cache API 7.x-1.4

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

Solution

Install the latest version:

Also see the Session Cache API 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

Better field descriptions - Critical - XSS - SA-CONTRIB-2017-064

Wed, 08/09/2017 - 9:51am
Description

This module enables you to add themeable descriptions to fields in forms.

The module doesn't sufficiently sanitize descriptions.

This vulnerability is mitigated by the fact that an attacker must have a role with the permission "add better descriptions to fields".

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

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

Solution

Install the latest version:

Also see the Better field descriptions 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

Relation - Moderately Critical - Access Bypass - DRUPAL-SA-CONTRIB-2017-063

Wed, 08/09/2017 - 9:46am
Description

This module enables you to store relationships between entities as fieldable entities.

The module doesn't sufficiently check permissions when displaying related entities labels with the Relation Dummy Field module widget.

This vulnerability is mitigated by the fact that the optional Relation Dummy Field module must be enabled and any entity must be configured to display related entities with the widget provided by the module.

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

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

Solution

Install the latest version:

Also see the Relation 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

services_views - Unsupported - SA-CONTRIB-2017-062

Wed, 08/02/2017 - 10:18am
  • Advisory ID: DRUPAL-SA-CONTRIB-2017-062
  • Project: services_views (third-party module)
  • Date: 2-Aug-2017
Description

This module provides views support for the Services module.

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 services_views module, there is nothing you need to do.

Solution

If you use the services_views module for Drupal you should uninstall it.

Also see the services_views 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

ajax_facets - Unsupported - SA-CONTRIB-2017-061

Wed, 08/02/2017 - 10:15am
  • Advisory ID: DRUPAL-SA-CONTRIB-2017-061
  • Project: ajax_facets (third-party module)
  • Date: 2-Aug-2017
Description

This module allows you to create facet filters which working by AJAX. Filters and search results will be updated by AJAX.

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 ajax_facets module, there is nothing you need to do.

Solution

If you use the ajax_facets module for Drupal you should uninstall it.

Also see the ajax_facets 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

baidu_analytics - Unsupported - SA-CONTRIB-2017-060

Wed, 08/02/2017 - 10:11am
  • Advisory ID: DRUPAL-SA-CONTRIB-2017-060
  • Project: baidu_analytics (third-party module)
  • Date: 2-Aug-2017
Description

This module adds the Baidu Analytics web statistics tracking system to your website.

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 baidu_analytics module, there is nothing you need to do.

Solution

If you use the baidu_analytics module for Drupal you should uninstall it.

Also see the baidu_analytics 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

html_title - Unsupported - SA-CONTRIB-2017-059

Wed, 08/02/2017 - 10:08am
  • Advisory ID: DRUPAL-SA-CONTRIB-2017-059
  • Project: html_title (third-party module)
  • Date: 2-Aug-2017
Description

The HTML Title module allows a limited set of HTML markup (em, sub, sup, b, i, strong, cite, code, bdi, wbr) to be used in node titles.

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 html_title module, there is nothing you need to do.

Solution

If you use the html_title module for Drupal you should uninstall it.

Also see the html_title 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

Alinks - Moderately Critical -Access bypass - SA-CONTRIB-2017-058

Wed, 08/02/2017 - 10:00am
Description

This module enables you to automatically link keywords to specific URLs.

This module has an insufficient access check on the delete route.

Alinks uses the wrong permission for an access check.

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

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

Solution

Install the latest version:

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

Also see the Alinks 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

DrupalChat - Critical - Multiple vulnerabilities - SA-CONTRIB-2017-057

Wed, 07/05/2017 - 12:40pm
Description

DrupalChat allows visitors of your Drupal site to chat with each other privately or together in a public chatroom.

The module did not confirm the validity of a chat request, resulting in a Cross Site Request Forgery (CSRF) vulnerability which enables an attacker to trick a user to send arbitrary chat messages to any user. The

The module did not filter administrator provided text, leading to a Cross Site Scripting (XSS) vulnerability.

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

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

Solution

Install the latest version:

Also see the DrupalChat project page.

Also see the DrupalChat 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

OAuth - Critical - Access Bypass - SA-CONTRIB-2017-056

Wed, 07/05/2017 - 12:17pm
Description

This module enables you to protect requests via the OAuth authentication protocol.

The module doesn't sufficiently notify the Cache API to avoid caching responses under the scenario in which an authenticated user requests a resource such as unpublished node.

This vulnerability is mitigated by the fact that an attacker must know the available resources in a Drupal site.

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

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

Solution

In addition to updating the code, you must Clear all caches.

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

Also see the OAuth 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

SMTP - Moderatley Critical - Information Disclosure - SA-CONTRIB-2017-055

Wed, 06/28/2017 - 9:43am
Description

This SMTP module enables you to send mail using a third party (non-system) mail service instead of the local system mailer included with Drupal. When this module is in debugging mode, it will log privileged information.

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

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

Solution

Install the latest version:

Also see the SMTP Authentication Support 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

Services - Critical - SQL Injection - SA-CONTRIB-2017-054

Wed, 06/28/2017 - 9:36am
Description

This module provides a standardized solution for building API's so that external clients can communicate with Drupal.

The module doesn't sufficiently sanitize column names provided by the client when they are querying for data and trying to sort it.

This vulnerability is mitigated by the fact that a site must have an "Index" resource enabled and the attacker must know the endpoint's URL.

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

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

Solution

Install services version 7.x-3.20 of the module or disable any Index resources within your endpoint(s).

Also see the Services 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