View online: https://drupal.org/node/2248077

* Advisory ID: DRUPAL-SA-CONTRIB-2014-043 * Project: Custom Search [1] (third-party module) * Version: 6.x, 7.x * Date: 2014-April-23 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting

-------- DESCRIPTION ---------------------------------------------------------

The Custom Search module alters the default search box to provide some options like in advanced search, but directly in the search box.

The module doesn't sanitize taxonomy vocabulary labels before display leading to a persistent cross site scripting (XSS) vulnerability.

This vulnerability is mitigated by the fact that it requires the attacker to have the permission "administer taxonomy."

-------- CVE IDENTIFIER(S) ISSUED --------------------------------------------

* /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./

-------- VERSIONS AFFECTED ---------------------------------------------------

* Custom Search 6.x-1.x versions prior to 6.x-1.13. * Custom Search 7.x-1.x versions prior to 7.x-1.15.

Drupal core is not affected. If you do not use the contributed Custom Search [4] module, there is nothing you need to do.

-------- SOLUTION ------------------------------------------------------------

Install the latest version:

* If you use the Custom Search module for Drupal 6.x, upgrade to Custom Search 6.x-1.13 [5] * If you use the Custom Search module for Drupal 7.x, upgrade to Custom Search 7.x-1.16 [6]

Also see the Custom Search [7] project page.

-------- REPORTED BY ---------------------------------------------------------

* Dennis Walgaard [8]

-------- FIXED BY ------------------------------------------------------------

* Dennis Walgaard [9]

-------- 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/custom_search [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/custom_search [5] http://drupal.org/node/2247919 [6] http://drupal.org/node/2247921 [7] http://drupal.org/project/custom_search [8] http://drupal.org/user/883702 [9] http://drupal.org/user/883702 [10] http://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