View online: https://www.drupal.org/node/2782023 * Advisory ID: DRUPAL-SA-CONTRIB-2016-042 * Project: Google Analytics [1] (third-party module) * Version: 7.x, 8.x * Date: 2016-August-10 * Security risk: 13/25 ( Moderately Critical) AC:None/A:Admin/CI:Some/II:Some/E:Theoretical/TD:Uncommon [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module enables you to add integration with Google Analytics statistics service. The module allows admin users to enter custom JavaScript snippets to add advanced tracking functionality. The permission required to enter this JavaScript was not marked as restricted. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "Administer Google Analytics". For greater flexibility a new feature has been added to the module to implement the new permission "Add JavaScript snippets" that can be assigned to users who are allowed to add JS code snippets into your web site. If you have granted the Administer Google Analytics to non trusted users, please check your settings to make sure all javascript entered is valid. -------- 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.x versions prior to 7.x-2.3. * Google Analytics 8.x-2.x versions prior to 8.x-2.1. 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.3 [5] * If you use the Google Analytics module for Drupal 8.x, upgrade to Google Analytics 8.x-2.1 [6] Also see the Google Analytics [7] project page. -------- REPORTED BY --------------------------------------------------------- * Michael Hess [8] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Lee Rowlands [9] of the Drupal Security Team * Alexander Hass [10] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Michael Hess [11] 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/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/project/google_analytics/releases/7.x-2.3 [6] https://www.drupal.org/project/google_analytics/releases/8.x-2.1 [7] https://www.drupal.org/project/google_analytics [8] https://www.drupal.org/u/mlhess [9] https://www.drupal.org/u/larowlan [10] https://www.drupal.org/u/hass [11] https://www.drupal.org/u/mlhess [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