[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20120509175053.897D5108051@www2.drupal.org>
Date: Wed, 9 May 2012 17:50:53 +0000 (UTC)
From: security-news@...pal.org
To: security-news@...pal.org
Subject: [Security-news] SA-CONTRIB-2012-075 - Take
Control - Cross Site Request Forgery (CSRF)
View online: http://drupal.org/node/1569512
* Advisory ID: DRUPAL-SA-CONTRIB-2012-075
* Project: Take Control [1] (third-party module)
* Version: 6.x
* Date: 2012-May-09
* Security risk: Critical [2]
* Exploitable from: Remote
* Vulnerability: Cross Site Request Forgery
-------- DESCRIPTION
---------------------------------------------------------
This module enables you to manage your Drupal file-system from within Drupal
itself.
The module does not sufficiently validate Ajax calls leading to possibility
of a Cross Site Request Forgery CSRF attack.
This vulnerability is mitigated by the fact that the attacker must be able to
guess your Drupal file-system root path exactly. Further, if your site
follows the secure file-system permissions recommendations [3] and the
web-server account does not have write access to Drupal root, only
files/folders in Drupal's "files" directory are open to manipulation.
-------- VERSIONS AFFECTED
---------------------------------------------------
* Take Control 6.x-2.x versions prior to 6.x-2.2.
Drupal core is not affected. If you do not use the contributed Take Control
[4] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Take Control module for Drupal 6.x, upgrade to Take Control
6.x-2.2 [5]
Also see the Take Control [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Carl Wiedemann [7]
-------- FIXED BY
------------------------------------------------------------
* Rahul Singla [8] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Greg Knaddison [9] of the Drupal Security Team
* Michael Hess [10] 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 [11].
Learn more about the Drupal Security team and their policies [12], writing
secure code for Drupal [13], and securing your site [14].
[1] http://drupal.org/project/take_control
[2] http://drupal.org/security-team/risk-levels
[3] http://drupal.org/node/244924
[4] http://drupal.org/project/take_control
[5] http://drupal.org/node/1243604
[6] http://drupal.org/project/take_control
[7] http://drupal.org/user/235047
[8] http://drupal.org/user/473356
[9] http://drupal.org/user/36762
[10] http://drupal.org/user/102818
[11] http://drupal.org/contact
[12] http://drupal.org/security-team
[13] http://drupal.org/writing-secure-code
[14] http://drupal.org/security/secure-configuration
_______________________________________________
Security-news mailing list
Security-news@...pal.org
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