View online: http://drupal.org/node/1802230
* Advisory ID: DRUPAL-SA-CONTRIB-2012-150 * Project: Twitter Pull [1] (third-party module) * Version: 6.x, 7.x * Date: 2012-October-03 * Security risk: Less critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting
-------- DESCRIPTION ---------------------------------------------------------
Twitter Pull allows you to retrieve tweets from Twitter based on a user or search and display them on your site. It also includes integration with the boxes module to allow for simple placement of twitter feeds on various pages.
The module doesn't sufficiently filter the data coming from Twitter which could result in script injection and XSS attacks.
This vulnerability is mitigated by the fact that Twitter is a generally trusted source and is unlikely to serve malicious content.
CVE: Requested
-------- VERSIONS AFFECTED ---------------------------------------------------
* Twitter Pull 6.x-1.x versions prior to 6.x-1.3. * Twitter Pull 7.x-1.x versions prior to 7.x-1.0-rc3.
Drupal core is not affected. If you do not use the contributed Twitter Pull [3] module, there is nothing you need to do.
Drupal core is not affected. If you do not use the contributed Twitter Pull [4] module, there is nothing you need to do.
-------- SOLUTION ------------------------------------------------------------
Install the latest version:
* If you use the Twitter Pull module for Drupal 6.x, upgrade to Twitter Pull 6.x-1.3 [5] * If you use the Twitter Pull module for Drupal 7.x, upgrade to Twitter Pull 7.x-1.0-rc3 [6]
Also see the Twitter Pull [7] project page.
-------- REPORTED BY ---------------------------------------------------------
* Sylvain Delbosc [8] * Alex Pott [9] * Tom Phethean [10]
-------- FIXED BY ------------------------------------------------------------
* Sylvain Delbosc [11] * Josh Caldwell [12] the module maintainer
-------- COORDINATED BY ------------------------------------------------------
* Greg Knaddison [13] 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 [14].
Learn more about the Drupal Security team and their policies [15], writing secure code for Drupal [16], and securing your site [17].
[1] http://drupal.org/project/twitter_pull [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/twitter_pull [4] http://drupal.org/project/twitter_pull [5] http://drupal.org/node/1801442 [6] http://drupal.org/node/1801444 [7] http://drupal.org/project/twitter_pull [8] http://drupal.org/user/174778 [9] http://drupal.org/user/157725 [10] http://drupal.org/user/881620 [11] http://drupal.org/user/174778 [12] http://drupal.org/user/855980 [13] http://drupal.org/user/27 [14] http://drupal.org/contact [15] http://drupal.org/security-team [16] http://drupal.org/writing-secure-code [17] http://drupal.org/security/secure-configuration