[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20121114212312.39F6C26804A@www6.drupal.org>
Date: Wed, 14 Nov 2012 21:23:12 +0000 (UTC)
From: security-news@...pal.org
To: security-news@...pal.org
Subject: [Security-news] SA-CONTRIB-2012-163 - User
Read-Only - Permission escalation
View online: http://drupal.org/node/1840886
* Advisory ID: DRUPAL-SA-CONTRIB-2012-163
* Project: User Read-Only [1] (third-party module)
* Version: 6.x, 7.x
* Date: 2012-November-14
* Security risk: Moderately critical [2]
* Exploitable from: Remote
* Vulnerability: Access bypass
-------- DESCRIPTION
---------------------------------------------------------
User Read-only is a module that allows an administrator to prevent
modification of user account/profile fields. The administrator can select
which fields will allow or disallow editing.
The module can mistakenly assign roles when performing unrelated operations
against a user's account such as changing a password.
The vulnerability is particular to certain combinations of configuration and
the number of roles available on the site (more than 3).
CVE: Requested
-------- VERSIONS AFFECTED
---------------------------------------------------
* User Read-Only 6.x-1.x versions prior to 6.x-1.4.
* User Read-Only 7.x-1.x versions prior to 7.x-1.4.
Drupal core is not affected. If you do not use the contributed User Read-Only
[3] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the User Read-Only module for Drupal 6.x, upgrade to User
Read-Only 6.x-1.4 [4]
* If you use the User Read-Only module for Drupal 7.x, upgrade to User
Read-Only 7.x-1.4 [5]
Also see the User Read-Only [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Kellie Bradford Delaney [7]
-------- FIXED BY
------------------------------------------------------------
* David Norman [8] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Greg Knaddison [9] of the Drupal Security Team
* Heine Deelstra [10] of the Drupal Security Team
* Lee Rowlands [11] provisional member 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/user_readonly
[2] http://drupal.org/security-team/risk-levels
[3] http://drupal.org/project/user_readonly
[4] http://drupal.org/node/1840054
[5] http://drupal.org/node/1840038
[6] http://drupal.org/project/user_readonly
[7] http://drupal.org/user/1473110
[8] http://drupal.org/user/972
[9] http://drupal.org/user/36762
[10] http://drupal.org/user/17943
[11] http://drupal.org/user/395439
[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