View online: https://www.drupal.org/node/2603560 * Advisory ID: DRUPAL-SA-CONTRIB-2015-161 * Project: Field as Block [1] (third-party module) * Version: 7.x * Date: 2015-October-28 * Security risk: 8/25 ( Less Critical) AC:Basic/A:Admin/CI:Some/II:None/E:Theoretical/TD:Uncommon [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- This module enables you to take a field from the current entity and place it elsewhere as a block. The module caches the block output in a manner that could allow sensitive content to be seen by visitors who should not see it. The problem will only occur when other modules alter field output based on user permissions. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Field as Block 7.x-1.x versions prior to 7.x-1.4. Drupal core is not affected. If you do not use the contributed Field as Block [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Field as Block module for Drupal 7.x, upgrade to Field as Block 7.x-1.4 [5] Also see the Field as Block [6] project page. -------- REPORTED BY --------------------------------------------------------- * László Csécsy [7] -------- FIXED BY ------------------------------------------------------------ * László Csécsy [8] * Marc van Gend [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Hunter Fox [10] of the Drupal Security Team * Greg Knaddison [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/fieldblock [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/fieldblock [5] https://www.drupal.org/node/2603420 [6] https://www.drupal.org/project/fieldblock [7] https://www.drupal.org/user/199303 [8] https://www.drupal.org/user/199303 [9] https://www.drupal.org/user/158153 [10] https://www.drupal.org/u/hefox [11] https://www.drupal.org/u/greggles [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