Message-Id: <20130626172655.E102D22803A@www7.drupal.org>
Date: Wed, 26 Jun 2013 17:26:55 +0000 (UTC)
From: security-news@...pal.org
To: security-news@...pal.org
Subject: [Security-news] SA-CONTRIB-2012-136 - Apache Solr
	Search	Autocomplete - Cross Site Scripting (XSS)

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

  * Advisory ID: DRUPAL-SA-CONTRIB-2012-136
  * Project: Apache Solr Autocomplete [1] (third-party module)
  * Version: 6.x, 7.x
  * Date: 2012-August-29
  * Security risk: Moderately critical [2]
  * Exploitable from: Remote
  * Vulnerability: Cross Site Scripting

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

Apache Solr Search Autocomplete module enables you to add autocomplete
capabilities to the search text field for the Apache Solr Search Integration
module.

The module doesn't sufficiently filter the autocomplete results sent back
from the Drupal site, so under the scenario where someone provided a URL with
a specially-crafted search string embedded in it, the attacker could have a
user execute arbitrary Javascript when clicking or focusing on the
autocomplete text field.

This vulnerability is mitigated by the fact that the attacked user must click
or otherwise give focus to the text widget to have the Javascript activate.

CVE: CVE-2012-6573

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

  * Apache Solr Autocomplete 6.x-1.x versions prior to 6.x-1.4.
  * Apache Solr Autocomplete 7.x-1.x versions prior to 7.x-1.3.

Drupal core is not affected. If you do not use the contributed Apache Solr
Autocomplete [3] module, there is nothing you need to do.

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

Install the latest version.

  * If you use the Apache Solr Autocomplete module for Drupal 6.x, upgrade to
    Apache Solr Autocomplete 6.x-1.4 [4]
  * If you use the Apache Solr Autocomplete module for Drupal 7.x, upgrade to
    Apache Solr Autocomplete 7.x-1.3 [5]

Also see the Apache Solr Autocomplete [6] project page.

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

  * drupaledmonk [7]

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

  * Alejandro Garza [8] the module maintainer

-------- COORDINATED BY  
------------------------------------------------------

  * Greg Knaddison [9] 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 [10].

Learn more about the Drupal Security team and their policies [11], writing
secure code for Drupal [12], and securing your site [13].


[1] http://drupal.org/project/apachesolr_autocomplete
[2] http://drupal.org/security-team/risk-levels
[3] http://drupal.org/project/apachesolr_autocomplete
[4] https://drupal.org/node/1762684
[5] https://drupal.org/node/1762686
[6] http://drupal.org/project/apachesolr_autocomplete
[7] http://drupal.org/user/263391
[8] http://drupal.org/user/153120
[9] http://drupal.org/user/36762
[10] http://drupal.org/contact
[11] http://drupal.org/security-team
[12] http://drupal.org/writing-secure-code
[13] http://drupal.org/security/secure-configuration

_______________________________________________
Security-news mailing list
Security-news@...pal.org
Unsubscribe at http://lists.drupal.org/mailman/listinfo/security-news

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

Powered by blists - more mailing lists