View online: https://www.drupal.org/node/2705637 * Advisory ID: DRUPAL-SA-CONTRIB-2016-020 * Project: Features [1] (third-party module) * Version: 7.x * Date: 2016-April-13 * Security risk: 7/25 ( Less Critical) AC:Basic/A:Admin/CI:None/II:None/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Request Forgery, Denial of Service -------- DESCRIPTION --------------------------------------------------------- This module enables you to organize and export configuration data. The module doesn't sufficiently protect the admin/structure/features/cleanup path with a token. If an attacker can trick an admin with the "manage features" permission to request a special URL, it could lead to clearing the cache repeatedly and a Denial of Service (DoS) attack. This vulnerability is mitigated by the fact that the admin with the "manage features" permissions must be logged in when they request the special URL. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Features 7.x-2.x versions prior to 7.x-2.9. * Features 7.x-1.x which is no longer supported. Drupal core is not affected. If you do not use the contributed Features [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Features module for Drupal 7.x, upgrade to Features 7.x-2.9 [5] Also see the Features [6] project page. -------- REPORTED BY --------------------------------------------------------- * James Kerrigan [7] -------- FIXED BY ------------------------------------------------------------ * James Kerrigan [8] * Mike Potter [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * David Snopek [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/features [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/features [5] https://www.drupal.org/node/2705595 [6] https://www.drupal.org/project/features [7] https://www.drupal.org/user/2511902 [8] https://www.drupal.org/user/2511902 [9] https://www.drupal.org/user/616192 [10] https://www.drupal.org/u/dsnopek [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