Drupal provides a mechanism to alter database SELECT queries before they are executed. Contributed and custom modules may use this mechanism to restrict access to certain entities by implementing hook_query_alter() or hook_query_TAG_alter() in order to add additional conditions. Queries can be distinguished by means of query tags. As the documentation on EntityFieldQuery::addTag() suggests, access-tags on entity queries normally follow the form ENTITY_TYPE_access (e.g. node_access). However, the taxonomy module's access query tag predated this system and used term_access as the query tag instead of taxonomy_term_access.

As a result, before this security release modules wishing to restrict access to taxonomy terms may have implemented an unsupported tag, or needed to look for both tags (term_access and taxonomy_term_access) in order to be compatible with queries generated both by Drupal core as well as those generated by contributed modules like Entity Reference. Otherwise information on taxonomy terms might have been disclosed to unprivileged users.

https://www.drupal.org/SA-CORE-2016-005

Now it's backward compatible but it's planned Emit E_USER_DEPRECATED if term_access is used.

CommentFileSizeAuthor
i18n-SA-CORE-2016-005-1.patch1.18 KBjansete
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jansete created an issue. See original summary.

jansete’s picture

Issue summary: View changes
joseph.olstad’s picture

so is this change backwards compatible with drupal core 7.51? or does it require drupal core 7.52?

joseph.olstad’s picture

OK reading description again says backwards compatible but I have not tried

  • joseph.olstad committed c5f60ad on 7.x-1.x authored by jansete
    Issue #2828383 by jansete: Inconsistent name for term access query - SA-...
joseph.olstad’s picture

Status: Needs review » Fixed

committed as-is to 7.x-1.x dev

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.