View online: http://drupal.org/node/1840892

  * Advisory ID: DRUPAL-SA-CONTRIB-2012-164
  * Project: Smiley [1] (third-party module)
  * Project: Smileys [2] (third-party module)
  * Version: 6.x
  * Date: 2012-November-14
  * Security risk: Moderately critical [3]
  * Exploitable from: Remote
  * Vulnerability: Cross Site Scripting

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

These modules enable you to substitutes text emoticons, like :-), with
images.

These modules don't sufficiently sanitize user defined smiley acronyms before
displaying smiley images.

This vulnerability is mitigated by the fact that an attacker must have a role
with the permission "administer smiley".

These two modules are based on the same codebase and Smiley was forked due to
lack of new feature development in the Smileys project. This single Security
Advisory covers the same issue in the code of both modules.

CVE: Requested

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

  * Smiley 6.x-1.x versions prior to 6.x-1.1.
  * Smileys 6.x-1.x versions prior to 6.x-1.1.

Drupal core is not affected. If you do not use the contributed Smiley [4]
module, or the Smileys [5] module there is nothing you need to do.

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

Install the latest version:

  * If you use the Smiley module for Drupal 6.x, upgrade to Smiley 6.x-1.1 [6]
  * If you use the Smileys module for Drupal 6.x, upgrade to Smileys 6.x-1.1
    [7]

Also see the Smiley [8] project page.

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

  * Jimmy Axenhus [9]

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

  * Yonas Yanfa [10] the module maintainer

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

  * Michael Hess [11] 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 [12].

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


[1] http://drupal.org/project/smiley
[2] http://drupal.org/project/smileys
[3] http://drupal.org/security-team/risk-levels
[4] http://drupal.org/project/smiley
[5] http://drupal.org/project/smileys
[6] http://drupal.org/node/1840956
[7] http://drupal.org/node/1840954
[8] http://drupal.org/project/smiley
[9] http://drupal.org/user/565562
[10] http://drupal.org/user/473174
[11] http://drupal.org/user/102818
[12] http://drupal.org/contact
[13] http://drupal.org/security-team
[14] http://drupal.org/writing-secure-code
[15] http://drupal.org/security/secure-configuration