SA-CONTRIB-2014-041 - Block Search - SQL Injection
View online: https://drupal.org/node/2242463 * Advisory ID: DRUPAL-SA-CONTRIB-2014-041 * Project: Block Search [1] (third-party module) * Version: 6.x * Date: 2014-April-16 * Security risk: Highly critical [2] * Exploitable from: Remote * Vulnerability: SQL Injection -------- DESCRIPTION --------------------------------------------------------- Block Search module provides an alternative way of managing blocks. The module doesn't properly use Drupal's database API resulting in user-provided strings being passed directly to the database allowing SQL Injection. This vulnerability is mitigated by the fact that an attacker must either use a CSRF attack against a user with sufficient permissions or have a role with the permission "admin blocks" or "set region". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Block Search All versions. Drupal core is not affected. If you do not use the contributed Block Search [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ No patch nor updated version is available. Site administrators should disable the module. Also see the Block Search [5] project page. -------- REPORTED BY --------------------------------------------------------- * Greg Knaddison [6] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ Not applicable. -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [7] 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 [8]. Learn more about the Drupal Security team and their policies [9], writing secure code for Drupal [10], and securing your site [11]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [12] [1] http://drupal.org/project/block_search [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/block_search [5] http://drupal.org/project/block_search [6] http://drupal.org/user/36762 [7] http://drupal.org/user/36762 [8] http://drupal.org/contact [9] http://drupal.org/security-team [10] http://drupal.org/writing-secure-code [11] http://drupal.org/security/secure-configuration [12] https://twitter.com/drupalsecurity
participants (1)
-
security-news@drupal.org