- Security-news - lists.drupal.org

SA-CONTRIB-2014-125 - Organic Groups Menu - Access bypass
by security-news＠drupal.org 10 Dec '14

10 Dec '14

View online: https://www.drupal.org/node/2390899 * Advisory ID: DRUPAL-SA-CONTRIB-2014-125 * Project: OG Menu [1] (third-party module) * Version: 6.x, 7.x * Date: 2014-December-10 * Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Access bypass, Information Disclosure -------- DESCRIPTION --------------------------------------------------------- This module enables you to associate menus with Organic Groups (OG). It allows you to create one or more menus per group, configure and apply menu permissions in a group context, add/edit menu links directly from the entity form, etc. The module doesn't sufficiently check the menu parameters passed in the path, creating an access bypass vulnerability allowing an attacker to edit or delete any menu link on the site. There is also an information disclosure vulnerability of menu info. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer og menu". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Organic Groups Menu (OG Menu) 6.x-2.x versions prior to 6.x-2.5. * Organic Groups Menu (OG Menu) 7.x-2.x versions prior to 7.x-2.3. * Organic Groups Menu (OG Menu) 7.x-3.x versions prior to 7.x-3.0 Drupal core is not affected. If you do not use the contributed OG Menu [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the OG Menu module for Drupal 6.x, upgrade to OG Menu 6.x-2.5 [5] * If you use the OG Menu module for Drupal 7.x and the OG module 7.x-1.x, upgrade to OG Menu 7.x-2.3 [6] * If you use the OG Menu module for Drupal 7.x, and the OG module 7.x-2.x upgrade to OG Menu 7.x-3.0 [7] Also see the OG Menu [8] project page. -------- REPORTED BY --------------------------------------------------------- * Lars Schröter [9] -------- FIXED BY ------------------------------------------------------------ * Wim Vanheste [10] the module maintainer * Lars Schröter [11] -------- COORDINATED BY ------------------------------------------------------ * Ben Dougherty [12] 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 [13]. Learn more about the Drupal Security team and their policies [14], writing secure code for Drupal [15], and securing your site [16]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [17] [1] https://www.drupal.org/project/og_menu [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/og_menu [5] https://drupal.org/node/2390187 [6] https://www.drupal.org/node/2390193 [7] https://www.drupal.org/node/2390195 [8] https://www.drupal.org/project/og_menu [9] https://www.drupal.org/u/osopolar [10] https://www.drupal.org/u/rv0 [11] https://www.drupal.org/u/osopolar [12] https://www.drupal.org/user/1852732 [13] https://www.drupal.org/contact [14] https://www.drupal.org/security-team [15] https://www.drupal.org/writing-secure-code [16] https://www.drupal.org/security/secure-configuration [17] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-124 - Poll Chart - Cross Site Scripting (XSS)
by security-news＠drupal.org 10 Dec '14

10 Dec '14

View online: https://www.drupal.org/node/2390897 * Advisory ID: DRUPAL-SA-CONTRIB-2014-124 * Project: Poll Chart Block [1] (third-party module) * Version: 7.x * Date: 2014-December-10 * Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module enables users to have a block displaying the result of the last poll as a chart. The module doesn't sufficiently sanitize poll node titles when displaying the block. This vulnerability is mitigated by the fact that an attacker must have a role with the permission to create polls and the poll chart block must be enabled. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * poll_chart 7.x-1.x versions prior to 7.x-1.2. Drupal core is not affected. If you do not use the contributed Poll Chart Block [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Poll Chart module for Drupal 7.x, upgrade to Poll Chart 7.x-1.2 [5] Also see the Poll Chart Block [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] -------- FIXED BY ------------------------------------------------------------ * CSÉCSY László [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Ben Dougherty [9] 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 [10]. Learn more about the Drupal Security team and their policies [11], writing secure code for Drupal [12], and securing your site [13]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [14] [1] https://www.drupal.org/project/poll_chart [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/poll_chart [5] https://www.drupal.org/node/2390097 [6] https://www.drupal.org/project/poll_chart [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/199303 [9] https://www.drupal.org/user/1852732 [10] https://www.drupal.org/contact [11] https://www.drupal.org/security-team [12] https://www.drupal.org/writing-secure-code [13] https://www.drupal.org/security/secure-configuration [14] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-123 - Postal Code - Cross Site Scripting (XSS)
by security-news＠drupal.org 10 Dec '14

10 Dec '14

View online: https://www.drupal.org/node/2390857 * Advisory ID: DRUPAL-SA-CONTRIB-2014-123 * Project: Postal Code [1] (third-party module) * Version: 7.x * Date: 2014-December-10 * Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Postal Code module enables you to implement postal code validation for several countries. The module doesn't sufficiently sanitize certain data in the admin thereby opening a Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with a permission that allows adding or editing fields to entity types such as "administer taxonomy terms" or "administer content types". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Postal Code 7.x-1.x versions prior to 7.x-1.9. Drupal core is not affected. If you do not use the contributed Postal Code [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Postal Code module for Drupal 7.x, upgrade to Postal Code 7.x-1.9 [5] Also see the Postal Code [6] project page. -------- REPORTED BY --------------------------------------------------------- * Matt Vance [7] (provisional member of the Drupal Security Team) -------- FIXED BY ------------------------------------------------------------ * Jeremy Edgell [8] the module maintainer * Matt Vance [9] (provisional member of the Drupal Security Team) -------- COORDINATED BY ------------------------------------------------------ * Lee Rowlands [10] of the Drupal Security Team * 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/postal_code [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/postal_code [5] https://www.drupal.org/node/2390323 [6] https://www.drupal.org/project/postal_code [7] https://www.drupal.org/user/88338 [8] https://www.drupal.org/user/1854054 [9] https://www.drupal.org/user/88338 [10] https://www.drupal.org/user/395439 [11] https://www.drupal.org/user/1852732 [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-122 - MoIP - Cross Site Scripting (XSS)
by security-news＠drupal.org 10 Dec '14

10 Dec '14

View online: https://www.drupal.org/node/2390849 * Advisory ID: DRUPAL-SA-CONTRIB-2014-122 * Project: MoIP [1] (third-party module) * Version: 7.x * Date: 2014-December-10 * Security risk: 16/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module enables you to use Moip (a Brazilian payment method) with Drupal Commerce. The module doesn't sufficiently filter the data passed by the automatic notifications, leaving the possibility for a malicious user to insert Cross Site Scripting (xss) attacks. This vulnerability is mitigated by the fact that only sites running the dblog module are affected (this module is enabled by default). -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Moip 7.x-1.x versions prior to 7.x-1.4. Drupal core is not affected. If you do not use the contributed MoIP [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Moip module for Drupal 7.x, upgrade to Moip 7.x-1.4 [5] Also see the MoIP [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] -------- FIXED BY ------------------------------------------------------------ * Pedro Rocha [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [9] 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 [10]. Learn more about the Drupal Security team and their policies [11], writing secure code for Drupal [12], and securing your site [13]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [14] [1] https://www.drupal.org/project/moip [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/moip [5] https://www.drupal.org/node/2390699 [6] https://www.drupal.org/project/moip [7] https://security.drupal.org/user/34908 [8] https://www.drupal.org/user/218937 [9] https://www.drupal.org/u/greggles [10] https://www.drupal.org/contact [11] https://www.drupal.org/security-team [12] https://www.drupal.org/writing-secure-code [13] https://www.drupal.org/security/secure-configuration [14] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-121 - Godwin's Law - Cross-Site Scripting (XSS)
by security-news＠drupal.org 10 Dec '14

10 Dec '14

View online: https://www.drupal.org/node/2390839 * Advisory ID: DRUPAL-SA-CONTRIB-2014-121 * Project: Godwin's Law [1] (third-party module) * Version: 7.x * Date: 2014-December-10 * Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module enables you to execute arbitrary Javascript by adding the script to the title of a node. The module doesn't sufficiently sanitize Watchdog messages when viewing the detail view of a specific Watchdog notification. It improperly translated the message rather than using proper Watchdog message syntax. This vulnerability is mitigated by the fact that an attacker must have a role allowing them to create nodes or edit the title of an existing node. It is further mitigated in that the script is only executed by admins when viewing a Watchdog notice when using dblog module (syslog users are not affected). -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Godwin's Law 7.x-1.0. Drupal core is not affected. If you do not use the contributed Godwin's Law [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Godwin's Law module for Drupal 7.x, upgrade to Godwin's Law 7.x-1.1 [5] Also see the Godwin's Law [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] -------- FIXED BY ------------------------------------------------------------ * tobby [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [9] 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 [10]. Learn more about the Drupal Security team and their policies [11], writing secure code for Drupal [12], and securing your site [13]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [14] [1] https://www.drupal.org/project/godwins_law [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/godwins_law [5] https://www.drupal.org/node/2390191 [6] https://www.drupal.org/project/godwins_law [7] https://www.drupal.org/u/pere-orga [8] https://www.drupal.org/u/tobby [9] https://www.drupal.org/user/36762 [10] https://www.drupal.org/contact [11] https://www.drupal.org/security-team [12] https://www.drupal.org/writing-secure-code [13] https://www.drupal.org/security/secure-configuration [14] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-120 - Piwik Web Analytics - Information disclosure
by security-news＠drupal.org 10 Dec '14

10 Dec '14

View online: https://www.drupal.org/node/2390695 * Advisory ID: DRUPAL-SA-CONTRIB-2014-120 * Project: Piwik Web Analytics [1] (third-party module) * Version: 7.x * Date: 2014-December-10 * Security risk: 11/25 ( Moderately Critical) AC:None/A:User/CI:Some/II:None/E:Theoretical/TD:Uncommon [2] * Vulnerability: Information Disclosure -------- DESCRIPTION --------------------------------------------------------- This module enables you to integrate Drupal with Piwik Web Analytics. The module leaks the site specific hash salt to authenticated users when user-id tracking is turned on. This vulnerability is mitigated by the fact that user-id tracking must be turned on and the attacker needs to have an account on the site. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Piwik Web Analytics 7.x-2.6. Neither earlier nor later versions are affected. Drupal core is not affected. If you do not use the contributed Piwik Web Analytics [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Piwik Web Analytics module for Drupal 7.x, upgrade to Piwik Web Analytics 7.x-2.7 [5] Affected sites are urged to generate a new hash salt and store it in settings.php. .... Methods to generate a new hash salt * With drush: drush php-eval 'echo(drupal_random_key()) . "\n";' * With openssl: openssl rand -base64 32 .... How to replace the hash salt 1) Open your settings.php file (e.g., sites/default/settings.php 2) Locate the variable $drupal_hash_salt: <?php /** * Salt for one-time login links and cancel links, form tokens, etc. * [...] */ $drupal_hash_salt = 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'; ?> 3) Replace the value and safe the file 4) Flush all caches either from within the administrative UI (/Administration » Configuration » Development » Performance/) or by issuing drush cache-clear all .... Effects caused by replacing the hash salt * Passwort reset links generated before the new hash salt will not work anymore. Affected users need to request a new password reset link. * Existing image style urls will stop working. A cache flush is necessary such that all tags are updated. If immediate installation / regeneration of the hash salt is not possible, then disable user-id tracking at once. Also see the Piwik Web Analytics [6] project page. -------- REPORTED BY --------------------------------------------------------- * znerol [7] -------- FIXED BY ------------------------------------------------------------ * Alexander Hass [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Klaus Purer [9] 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 [10]. Learn more about the Drupal Security team and their policies [11], writing secure code for Drupal [12], and securing your site [13]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [14] [1] https://www.drupal.org/project/piwik [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/piwik [5] https://www.drupal.org/node/2384237 [6] https://www.drupal.org/project/piwik [7] https://www.drupal.org/user/63999 [8] https://www.drupal.org/user/85918 [9] https://www.drupal.org/user/262198 [10] https://www.drupal.org/contact [11] https://www.drupal.org/security-team [12] https://www.drupal.org/writing-secure-code [13] https://www.drupal.org/security/secure-configuration [14] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-119 - Google Analytics - Information disclosure
by security-news＠drupal.org 10 Dec '14

10 Dec '14

View online: https://www.drupal.org/node/2390689 * Advisory ID: DRUPAL-SA-CONTRIB-2014-119 * Project: Google Analytics [1] (third-party module) * Version: 7.x * Date: 2014-December-10 * Security risk: 11/25 ( Moderately Critical) AC:None/A:User/CI:Some/II:None/E:Theoretical/TD:Uncommon [2] * Vulnerability: Information Disclosure -------- DESCRIPTION --------------------------------------------------------- This module enables you to integrate Drupal with Google Analytics. The module leaks the site specific hash salt to authenticated users when user-id tracking is turned on. This vulnerability is mitigated by the fact that user-id tracking must be turned on and the attacker needs to have an account on the site. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Google Analytics 7.x-2.0. Neither earlier nor later versions are affected. Drupal core is not affected. If you do not use the contributed Google Analytics [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Google Analytics module for Drupal 7.x, upgrade to Google Analytics 7.x-2.1 [5] Affected sites are urged to generate a new hash salt and store it in settings.php. .... Methods to generate a new hash salt * With drush: drush php-eval 'echo(drupal_random_key()) . "\n";' * With openssl: openssl rand -base64 32 .... How to replace the hash salt 1) Open your settings.php file (e.g., sites/default/settings.php 2) Locate the variable $drupal_hash_salt: <?php /** * Salt for one-time login links and cancel links, form tokens, etc. * [...] */ $drupal_hash_salt = 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'; ?> 3) Replace the value and safe the file 4) Flush all caches either from within the administrative UI (/Administration » Configuration » Development » Performance/) or by issuing drush cache-clear all .... Effects caused by replacing the hash salt * Passwort reset links generated before the new hash salt will not work anymore. Affected users need to request a new password reset link. * Existing image style urls will stop working. A cache flush is necessary such that all tags are updated. If immediate installation / regeneration of the hash salt is not possible, then disable user-id tracking at once. Also see the Google Analytics [6] project page. -------- REPORTED BY --------------------------------------------------------- * Alexander Hass [7] the module maintainer * znerol [8] -------- FIXED BY ------------------------------------------------------------ * Alexander Hass [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Klaus Purer [10] 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 [11]. Learn more about the Drupal Security team and their policies [12], writing secure code for Drupal [13], and securing your site [14]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15] [1] https://www.drupal.org/project/google_analytics [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/google_analytics [5] https://www.drupal.org/node/2384245 [6] https://www.drupal.org/project/google_analytics [7] https://www.drupal.org/user/85918 [8] https://www.drupal.org/user/63999 [9] https://www.drupal.org/user/85918 [10] https://www.drupal.org/user/262198 [11] https://www.drupal.org/contact [12] https://www.drupal.org/security-team [13] https://www.drupal.org/writing-secure-code [14] https://www.drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity

1 0

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