[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20120620174444.719C11D00A1@www1.drupal.org>
Date: Wed, 20 Jun 2012 17:44:44 +0000 (UTC)
From: security-news@...pal.org
To: security-news@...pal.org
Subject: [Security-news] SA-CONTRIB-2012-104 - Privatemsg
- Cross Site Scripting (XSS)
View online: http://drupal.org/node/1649346
* Advisory ID: DRUPAL-SA-CONTRIB-2012-104
* Project: Privatemsg [1] (third-party module)
* Version: 7.x
* Date: 2012-June-20
* Security risk: Moderately critical [2]
* Exploitable from: Remote
* Vulnerability: Cross Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
The Privatemsg module allows users to send private messages between to each
other. The module doesn't sufficiently sanitize user names when creating
messages.
This vulnerability is mitigated by the fact that it is not possible to create
insecure user names through the default user interface. The exploit is only
possible in combination with another module that allows this, such as
Realname [3] which allows site-builders to choose fields to display an
alternative username.
CVE: Requested
-------- VERSIONS AFFECTED
---------------------------------------------------
* Privatemsg 7.x-1.x versions prior to 7.x-1.3
Drupal core is not affected. If you do not use the contributed Privatemsg [4]
module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Privatemsg module for Drupal 7, upgrade to Privatemsg
7.x-1.3 [5]
Also see the Privatemsg [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Dave Reid [7] of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
* Sascha Grossenbacher [8] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Dave Reid [9] of the Drupal Security Team
* Greg Knaddison [10] of the Drupal Security Team
* 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/privatemsg
[2] http://drupal.org/security-team/risk-levels
[3] http://drupal.org/project/realname
[4] http://drupal.org/project/privatemsg
[5] http://drupal.org/node/1649338
[6] http://drupal.org/project/privatemsg
[7] http://drupal.org/user/53892
[8] http://drupal.org/user/214652
[9] http://drupal.org/user/53892
[10] http://drupal.org/user/36762
[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
_______________________________________________
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