Security-news December 2014

security-news@drupal.org

1 participants
13 discussions

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

17 Dec '14

View online: https://www.drupal.org/node/2395049 * Advisory ID: DRUPAL-SA-CONTRIB-2014-128 * Project: OG Menu [1] (third-party module) * Version: 6.x, 7.x * Date: 2014-December-17 * 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". *This handles the same issue as SA-CONTRIB-2014-125 [3], but due to a mistake made in tagging the release, the fix did not get included.* -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [4] 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.6 * Organic Groups Menu (OG Menu) 7.x-2.x versions prior to 7.x-2.4 Organic Groups Menu (OG Menu) 7.x-3.0 and later versions are not affected. Drupal core is not affected. If you do not use the contributed OG Menu [5] 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.6 [6] * 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.4 [7] * If you use the OG Menu module for Drupal 7.x and the OG module 7.x-2.x, no action is needed. Also see the OG Menu [8] project page. -------- REPORTED BY --------------------------------------------------------- * Marjolein de Waal [9] -------- FIXED BY ------------------------------------------------------------ * Wim Vanheste [10] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [11] of the Drupal Security Team * Klaus Purer [12] 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] https://www.drupal.org/node/2390899 [4] http://cve.mitre.org/ [5] https://www.drupal.org/project/og_menu [6] https://www.drupal.org/node/2394845 [7] https://www.drupal.org/node/2394847 [8] https://www.drupal.org/project/og_menu [9] https://www.drupal.org/user/2862205 [10] https://www.drupal.org/u/rv0 [11] https://www.drupal.org/u/greggles [12] https://www.drupal.org/u/klausi [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-127 - School Administration - Cross Site Scripting (XSS)
by security-news＠drupal.org 17 Dec '14

17 Dec '14

View online: https://www.drupal.org/node/2395015 * Advisory ID: DRUPAL-SA-CONTRIB-2014-127 * Project: (third-party module) * Version: 7.x * Date: 2014-December-17 * Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [1] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- School Administration module enables you to keep records of all students and staff. With inner modules, it aims to be a complete school administration system. The module failed to sanitize some node titles in messages, leading to a Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a user with the permission to create or edit a class node. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [2] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * School Administration 7.x-1.x versions prior to 7.x-1.8. Drupal core is not affected. If you do not use the contributed module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the School Administration module for Drupal 7.x, upgrade to School Administration 7.x-1.8 [3] Also see the project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [4] -------- FIXED BY ------------------------------------------------------------ * Murat Tutumlu [5] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [6] 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 [7]. Learn more about the Drupal Security team and their policies [8], writing secure code for Drupal [9], and securing your site [10]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [11] [1] https://www.drupal.org/security-team/risk-levels [2] http://cve.mitre.org/ [3] https://www.drupal.org/node/2391119 [4] https://www.drupal.org/user/2301194 [5] https://www.drupal.org/user/413570 [6] https://www.drupal.org/user/36762 [7] https://www.drupal.org/contact [8] https://www.drupal.org/security-team [9] https://www.drupal.org/writing-secure-code [10] https://www.drupal.org/security/secure-configuration [11] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-126 - Open Atrium - Multiple vulnerabilities
by security-news＠drupal.org 17 Dec '14

17 Dec '14

View online: https://www.drupal.org/node/2394979 * Advisory ID: DRUPAL-SA-CONTRIB-2014-126 * Project: Open Atrium [1] (third-party module) * Version: 7.x * Date: 2014-12-17 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Access bypass, Cross Site Request Forgery, Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- This distribution enables you to create an intranet. Several of the sub modules included do not prevent CSRF on several menu callbacks. Open Atrium Discussion also does not exit correctly after checking access on a several ajax callbacks, allowing anyone with "access content" to update and delete nodes. Also, (alpha) module OG Subgroups contained a vulnerability that allowed access to child groups even if membership inheritance was disabled. The vulnerabilities are mitigated by needing the sub modules enabled -- Open Atrium Sitemap [3], Open Atrium Discussion [4], and OpenA trium Admin Role and OA Teams, modules bundled with of Open Atrium Core [5]. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [6] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Open Atrium 7.x-2.x versions prior to 7.x-2.26 Drupal core is not affected. If you do not use the contributed Open Atrium [7] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Open Atrium Distro for Drupal 7.x, upgrade to Open Atrium 7.x-2.26 [8] Also see the Open Atrium [9] project page. -------- REPORTED BY --------------------------------------------------------- * Hunter Fox [10] of the Drupal Security Team & an Open Atrium maintainer * Pere Orga [11] -------- FIXED BY ------------------------------------------------------------ * Hunter Fox [12] of the Drupal Security Team & an Open Atrium maintainer -------- COORDINATED BY ------------------------------------------------------ * Hunter Fox [13] of the Drupal Security Team & an Open Atrium maintainer -------- 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/openatrium [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/oa_sitemap [4] https://www.drupal.org/project/oa_discussion [5] https://www.drupal.org/project/oa_core [6] http://cve.mitre.org/ [7] https://www.drupal.org/project/openatrium [8] https://www.drupal.org/node/2395045 [9] https://www.drupal.org/project/openatrium [10] https://www.drupal.org/user/426416 [11] https://www.drupal.org/user/2301194 [12] https://www.drupal.org/user/426416 [13] https://www.drupal.org/user/426416 [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

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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Security-news December 2014