View online: https://www.drupal.org/node/2841094
* Advisory ID: DRUPAL-SA-CONTRIB-2017-001 * Project: Permissions by Term [1] (third-party module) * Version: 8.x * Date: 2017-January-04 * Security risk: 15/25 ( Critical) AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:All [2] * Vulnerability: Access bypass, Information Disclosure
-------- DESCRIPTION ---------------------------------------------------------
The Permissions by Term module extends Drupal functionality by restricting access to single nodes via taxonomy terms. Taxonomy terms are part of the Drupal core functionality. Taxonomy term permissions can be coupled to specific user accounts and/or user roles.
Enabling the module unintentionally gives access to all unpublished nodes to anonymous users
-------- CVE IDENTIFIER(S) ISSUED --------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED ---------------------------------------------------
* Permissions by Term 8.x-1.x versions prior to 8.x-1.11.
Drupal core is not affected. If you do not use the contributed Permissions by Term [4] module, there is nothing you need to do.
-------- SOLUTION ------------------------------------------------------------
If you use the Permissions by Term module for Drupal 8.x, upgrade to Permissions by Term 8.x-1.11. [5]
Also see the Permissions by Term [6] project page.
-------- REPORTED BY ---------------------------------------------------------
* cedric_a [7]
-------- FIXED BY ------------------------------------------------------------
* Peter Majmesku (jepSter) [8] - the module maintainer
-------- COORDINATED BY ------------------------------------------------------
* Michael Hess [9] 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 https://www.drupal.org/contact [10].
Learn more about the Drupal Security team and their policies [11], writing secure code for Drupal [12], and securing your site [13].
Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [14]
[1] https://www.drupal.org/project/permissions_by_term [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/permissions_by_term [5] https://www.drupal.org/project/permissions_by_term/releases/8.x-1.11 [6] https://www.drupal.org/project/permissions_by_term [7] https://www.drupal.org/u/cedric_a [8] https://www.drupal.org/u/jepster [9] https://www.drupal.org/u/mlhess [10] https://www.drupal.org/contact [11] https://www.drupal.org/security-team [12] https://www.drupal.org/writing-secure-code [13] https://www.drupal.org/security/secure-configuration [14] https://twitter.com/drupalsecurity