View online: https://drupal.org/node/2236807
* Advisory ID: DRUPAL-SA-CONTRIB-2014-039 * Project: Revisioning [1] (third-party module) * Version: 7.x * Date: 2014-April-09 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Access bypass
-------- DESCRIPTION ---------------------------------------------------------
This module enables you to manage publication workflows whereby new, not publicly visible revisions of existing published content may be created by an author for review, while the current revision remains live to the public. The new revision does not go live until it is approved by a moderator with the necessary privileges to publish the new revision, replacing the old.
The module didn't properly invoke access grants introduced by other contributed modules. Instead it gives "view" access to published content and does not enforce view access restrictions imposed by other modules.
This vulnerability is mitigated by the fact that this is only an issue when your site uses modules that introduce additional access grants over and above core's access permissions, such as Taxonomy Access or Content Access.
-------- CVE IDENTIFIER(S) ISSUED --------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED ---------------------------------------------------
* Revisioning version 7.x-1.7 only
Drupal core is not affected. If you do not use the contributed Revisioning [4] module, there is nothing you need to do.
-------- SOLUTION ------------------------------------------------------------
Install the latest version:
* If you use the Revisioning module 7.x-1.7, upgrade to 7.x-1.8 [5]. Revisioning 7.x-1.6 does not have the bug, but reverting to 7.x-1.6 naturally also means you miss out on any bug-fixes and features of version 7.x-1.7
Also see the Revisioning [6] project page.
-------- REPORTED BY ---------------------------------------------------------
* Ryan Jacobs [7]
-------- FIXED BY ------------------------------------------------------------
* Rik de Boer [8], the module maintainer * Ryan Jacobs [9]
-------- COORDINATED BY ------------------------------------------------------
* Mark Ferree [10] 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 [11].
Learn more about the Drupal Security team and their policies [12], writing secure code for Drupal [13], and securing your site [14].
Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15]
[1] http://drupal.org/project/revisioning [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/revisioning [5] https://drupal.org/node/2235477 [6] http://drupal.org/project/revisioning [7] https://drupal.org/user/422459 [8] http://drupal.org/user/404007 [9] https://drupal.org/user/422459 [10] http://drupal.org/user/76245 [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 [15] https://twitter.com/drupalsecurity