December 2014 - Security-news

SA-CONTRIB-2014-118 - Administer Users by Role - Access Bypass - Unsupported
by security-news＠drupal.org 10 Dec '14

10 Dec '14

View online: https://www.drupal.org/node/2390687 * Advisory ID: DRUPAL-SA-CONTRIB-2014-118 * Project: Administer Users by Role [1] (third-party module) * Version: 6.x * Date: 2014-December-10 * Security risk: 11/25 ( Moderately Critical) AC:Complex/A:Admin/CI:None/II:All/E:Proof/TD:Default [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- 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 [3] 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 [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ * If you use the administerusersbyrole module for Drupal 6.x, disable and uninstall the module Also see the Administer Users by Role [5] project page. -------- REPORTED BY --------------------------------------------------------- * Adam Shepherd [6] -------- FIXED BY ------------------------------------------------------------ not applicable. -------- COORDINATED BY ------------------------------------------------------ * Klaus Purer [7] of the Drupal Security Team -------- 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 [8]. Learn more about the Drupal Security team and their policies [9], writing secure code for Drupal [10], and securing your site [11]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [12] [1] https://www.drupal.org/project/administerusersbyrole [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/administerusersbyrole [5] https://www.drupal.org/project/administerusersbyrole [6] https://www.drupal.org/u/adamps [7] https://www.drupal.org/u/klausi [8] https://www.drupal.org/contact [9] https://www.drupal.org/security-team [10] https://www.drupal.org/writing-secure-code [11] https://www.drupal.org/security/secure-configuration [12] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-116 -Webform Invitation - Cross Site Scripting
by security-news＠drupal.org 03 Dec '14

03 Dec '14

View online: https://www.drupal.org/node/2386387 * Advisory ID: DRUPAL-SA-CONTRIB-2014-116 * Project: Webform Invitation [1] (third-party module) * Version: 7.x * Date: 2014-December-03 * Security risk: 8/25 ( Less Critical) AC:Basic/A:User/CI:None/II:None/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- 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 [3] 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 [4] 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 [5] * 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 [6] Also see the Webform Invitation [7] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [8] -------- FIXED BY ------------------------------------------------------------ * Christian Paul Bruhn [9] the module maintainer * Pere Orga [10] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Ben Dougherty [11] provisional member of the Drupal Security Team -------- 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 [12]. Learn more about the Drupal Security team and their policies [13], writing secure code for Drupal [14], and securing your site [15]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [16] [1] https://www.drupal.org/project/webform_invitation [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/webform_invitation [5] https://www.drupal.org/node/2386011 [6] https://www.drupal.org/node/2386013 [7] https://www.drupal.org/project/webform_invitation [8] https://www.drupal.org/user/2301194 [9] https://www.drupal.org/user/519108/ [10] https://www.drupal.org/user/2301194 [11] https://www.drupal.org/u/benjy [12] https://www.drupal.org/contact [13] https://www.drupal.org/security-team [14] https://www.drupal.org/writing-secure-code [15] https://www.drupal.org/security/secure-configuration [16] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-117 - Hierarchical Select - Cross Site Scripting (XSS)
by security-news＠drupal.org 03 Dec '14

03 Dec '14

View online: https://www.drupal.org/node/2386615 * Advisory ID: DRUPAL-SA-CONTRIB-2014-117 * Project: Hierarchical Select [1] (third-party module) * Version: 6.x * Date: 2014-December-03 * Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:All/E:Theoretical/TD:Uncommon [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- 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 [3] 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 [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Hierarchical Select module for Drupal 6.x, upgrade to Hierarchical Select 6.x-3.9 [5] After installing the latest version, clear all caches so that no malicious code will linger in any cached data. Also see the Hierarchical Select [6] project page. -------- REPORTED BY --------------------------------------------------------- * Rodolfo Candido [7] * Stefan Ruijsenaars [8] * Matt Vance [9] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Stefan Ruijsenaars [10] the module maintainer * Matt Vance [11] provisional member of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Cash Williams [12] of the Drupal Security Team * Matt Vance [13] provisional member of the Drupal Security Team -------- 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 [14]. Learn more about the Drupal Security team and their policies [15], writing secure code for Drupal [16], and securing your site [17]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [18] [1] https://www.drupal.org/project/hierarchical_select [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/hierarchical_select [5] https://www.drupal.org/node/2385933 [6] https://www.drupal.org/project/hierarchical_select [7] https://www.drupal.org/user/479018 [8] https://www.drupal.org/u/stefan.r [9] https://www.drupal.org/u/matt-v [10] https://www.drupal.org/u/stefan.r [11] https://www.drupal.org/u/matt-v [12] https://www.drupal.org/u/cashwilliams [13] https://www.drupal.org/u/matt-v [14] https://www.drupal.org/contact [15] https://www.drupal.org/security-team [16] https://www.drupal.org/writing-secure-code [17] https://www.drupal.org/security/secure-configuration [18] https://twitter.com/drupalsecurity

1 0