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