This module enables site builders to set up fine-grained permissions for allowing users to edit and delete other users.
The module doesn’t sufficiently validate access permissions, enabling users who supposedly have limited permissions to grant themselves more permissions.
This vulnerability is mitigated by the fact that an attacker must have a role with the permission “administer users”. While this is usually a permission only granted to trusted users the Administer Users by Role module intends to limit the permission so that users cannot elevate their own permissions, but it fails to do so in certain scenarios.
CVE identifier(s) issued
A CVE identifier will be requested, and added upon issuance, in accordance
with Drupal Security Team processes.
Versions affected
administerusersbyrole 6.x – all versions
Drupal core is not affected. If you do not use the contributed Administer Users by Role module,
there is nothing you need to do.
Solution
If you use the administerusersbyrole module for Drupal 6.x, disable and uninstall the module
The Hierarchical Select module provides a “hierarchical_select” form element, which is a greatly enhanced way for letting the user select items in a taxonomy. The module does not sanitize some of the user-supplied data before displaying it, leading to two Cross Site Scripting (XSS) vulnerabilities that may lead to a malicious user gaining full administrative access.
The first vulnerability is mitigated by the fact that the attacker must have a role with the “administer taxonomy” permission; specifically the attacker must be able to create or modify taxonomy terms and then modify the term title. Only Hierarchical Select field instances with the “Save term lineage” option enabled in the widget settings are vulnerable.
The second vulnerability is mitigated by the fact that an attacker must have a permission to administer fields on an entity type, for example the “administer taxonomy” permission to manage fields on taxonomy terms, the “administer users” permission to manage fields on users or the “administer content type” permission to manage fields on comments or nodes.
CVE identifier(s) issued
A CVE identifier will be requested, and added upon issuance, in accordance
with Drupal Security Team processes.
Versions affected
Hierarchical Select 6.x versions prior to 6.x-3.9.
Drupal core is not affected. If you do not use the contributed Hierarchical Select module,
there is nothing you need to do.
This module enables you to create custom invitation codes for Webforms.
The module failed to sanitize node titles.
This vulnerability is mitigated by the fact that an attacker must have a role with the permission “Webform: Create new content”, “Webform: Edit own content” and/or “Webform: Edit any content”.
CVE identifier(s) issued
A CVE identifier will be requested, and added upon issuance, in accordance
with Drupal Security Team processes.
Versions affected
Webform Invitation 7.x-1.x versions prior to 7.x-1.3.
Webform Invitation 7.x-2.x versions prior to 7.x-2.4.
Drupal core is not affected. If you do not use the contributed Webform Invitation module,
there is nothing you need to do.
Solution
Install the latest version:
If you use the Webform Invitation module for Drupal 7.x and Webform 7.x-3.x, upgrade to Webform Invitation 7.x-1.3
If you use the Webform Invitation module for Drupal 7.x and Webform 7.x-4.x, upgrade to Webform Invitation 7.x-2.4
The Form Builder module enables users to build entire Form API structures through a graphical, AJAX-like interface.
The module doesn’t sufficiently sanitize form titles in some cases.
This vulnerability is mitigated by the fact that an attacker must have a role with the permission to create forms in another module that depends on Form Builder, such as Survey Builder, Webform, or others.
CVE identifier(s) issued
A CVE identifier will be requested, and added upon issuance, in accordance
with Drupal Security Team processes.
Versions affected
Form Builder 7.x-1.x versions prior to 7.x-1.6.
Form Builder 6.x-1.x versions prior to 6.x-1.6.
Drupal core is not affected. If you do not use the contributed Form Builder module,
there is nothing you need to do.
Solution
Install the latest version:
If you use the Form Builder module for Drupal 7.x, upgrade to Form Builder 7.x-1.6
If you use the Form Builder module for Drupal 6.x, upgrade to Form Builder 6.x-1.6
This project allows you to create various types of tournaments (as nodes) and associated teams, tournaments, and matches.
There are several cases in the project where an account username, node title, and team entity title are not correctly filtered before being displayed to a user.
It is possible to create nodes or entities containing XSS or usernames could be imported with XSS in the strings or created via an add-on module like LDAP or similar.
This vulnerability is mitigated by the fact that an attacker must have a role with the permissions “Create new teams” or “Tournament: Create new content” or “Match: Create new content” or the ability to create users with an XSS payload in the usernames (Drupal core’s input validation prevents XSS payloads in usernames).
CVE identifier(s) issued
A CVE identifier will be requested, and added upon issuance, in accordance
with Drupal Security Team processes.
Versions affected
Tournament 7.x-1.x any version
Drupal core is not affected. If you do not use the contributed Tournament module,
there is nothing you need to do.
Solution
Install the latest version:
If you use the Tournament module for Drupal 7.x, upgrade to Tournament 7.x-1.2
This module enables a more secure password storage for Drupal 6 by back-porting the code used in Drupal 7 core.
A vulnerability in this API allows an attacker to send specially crafted requests resulting in CPU and memory exhaustion. This may lead to the site becoming unavailable or unresponsive (denial of service).
This vulnerability can be exploited by anonymous users
A specially crafted request can give a user access to another user’s session, allowing an attacker to hijack a random session.
This attack is known to be possible on certain Drupal 7 sites which serve both HTTP and HTTPS content (“mixed-mode”), but it is possible there are other attack vectors for both Drupal 6 and Drupal 7.
Denial of service (Drupal 7 only)
Drupal 7 includes a password hashing API to ensure that user supplied passwords are not stored in plain text.
A vulnerability in this API allows an attacker to send specially crafted requests resulting in CPU and memory exhaustion. This may lead to the site becoming unavailable or unresponsive (denial of service).
This vulnerability can be exploited by anonymous users.
CVE identifier(s) issued
A CVE identifier will be requested, and added upon issuance, in accordance
with Drupal Security Team processes.
If you have configured a custom password.inc file for your Drupal 7 site you also need to make sure that it is not prone to the same denial of service vulnerability. See also the similar security advisory for the Drupal 6 contributed Secure Password Hashes module: SA-CONTRIB-2014-113
Node Field module allows you to add custom extra fields to single Drupal nodes.
The module doesn’t sufficiently sanitize user input for some of the module’s internal fields. This vulnerability is mitigated by the fact that an attacker must have a role with the permission to create nodes.
CVE identifier(s) issued
A CVE identifier will be requested, and added upon issuance, in accordance
with Drupal Security Team processes.
Versions affected
Node Field 7.x-2.x versions prior to 7.x-2.45.
Drupal core is not affected. If you do not use the contributed Node Field module,
there is nothing you need to do.
Solution
Install the latest version:
If you use the Node Field module for Drupal 7.x, upgrade to Node Field 7.x-2.45
The Freelinking module implements a filter framework for easier creation of HTML links to other pages on the site or to external sites.
The module does not sanitize the node title when providing a link to the node, opening a Cross Site Scripting (XSS) vulnerability.
This vulnerability is mitigated by the fact that the person creating the content containing the link must have a role that allows use of an unsafe text format (e.g. “Full HTML”), or the Freelinking filter must be placed after all text sanitizion filters (e.g. “Limit allowed HTML tags”) in an otherwise safe text format (e.g. “Filtered HTML”).
Please note that this vulnerability also existed the freelinking_nodetitle.inc in versions prior to 6.x-3.4 and 7.x-3.4, but this was patched in releases 6.x-3.4 and 7.x-3.4.
CVE identifier(s) issued
A CVE identifier will be requested, and added upon issuance, in accordance
with Drupal Security Team processes.
Versions affected
Freelinking 6.x-x.x versions prior to 6.x-3.5.
Freelinking 7.x-x.x versions prior to 7.x-3.5.
Drupal core is not affected. If you do not use the contributed Freelinking module,
there is nothing you need to do.
Solution
Install the latest version:
If you use the Freelinking module for Drupal 6.x, upgrade to Freelinking 6.x-3.5
If you use the Freelinking module for Drupal 7.x, upgrade to Freelinking 7.x-3.5
Please note that the plugin freelinking_path.inc contains multible vulnerabilities and was removed in the releases 6.x-3.3 and 7.x-3.3. You should check to see if this file is still present, and if it is: Remove it from the plugin sub-directory before you install the latest version.