[IT-SecNots] [Security-news] SA-CONTRIB-2014-119 - Google Analytics - Information disclosure

[security-news AT drupal.org]

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

_______________________________________________
Security-news mailing list
Security-news AT drupal.org
Unsubscribe at https://lists.drupal.org/mailman/listinfo/security-news