View online: https://drupal.org/node/2221403 * Advisory ID: DRUPAL-SA-CONTRIB-2014-032 * Project: Xapian integration [1] (third-party module) * Version: 6.x, 7.x * Date: 2014-March-19 * Security risk: Not critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- This module enables you to use Xapian system to do searches of a Xapian index from within drupal. The module doesn't verify node access rights when a node is loaded for display after the search happened in Xapian. This vulnerability is mitigated by the fact that the system must be using a node access control module. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Xapian integration 6.x-2.x versions prior to 6.x-2.2. * Xapian integration 7.x-2.x versions prior to 7.x-1.2. Drupal core is not affected. If you do not use the contributed Xapian integration [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Xapian integration module for Drupal 6.x, upgrade to Xapian integration 6.x-2.2 [5] * If you use the Xapian integration module for Drupal 7.x, upgrade to Xapian integration 7.x-1.2 [6] Also see the Xapian integration [7] project page. -------- REPORTED BY --------------------------------------------------------- * Antonello Lobianco [8]. -------- FIXED BY ------------------------------------------------------------ * Marco Villegas [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [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 http://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] http://drupal.org/project/xapian [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/xapian [5] https://drupal.org/node/2220483 [6] https://drupal.org/node/2220487 [7] http://drupal.org/project/xapian [8] https://drupal.org/user/170459 [9] http://drupal.org/user/132175 [10] https://drupal.org/user/36762 [11] http://drupal.org/contact [12] http://drupal.org/security-team [13] http://drupal.org/writing-secure-code [14] http://drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity