Description

This module enables you to build searches using a wide range of features, data sources and backends.

Search index not updated by node access changes

The module doesn't sufficiently re-index nodes when using the "Node access" or "Access check" data alterations and non-standard ways of changing node access are used. This could lead to nodes or comments being listed in search results to which the visitor viewing the results should not have access.

This vulnerability is mitigated by the fact that this only occurs in uncommon setups, and that only nodes that were already accessible to the user at some point can be displayed.

XSS vulnerability in Views search results

The module doesn't sufficiently sanitize field values returned directly from the search server (e.g., Solr).

This vulnerability is mitigated by the fact that several components/modules need to be configured in a specific way to allow this vulnerability to be exploited.

Doesn't check for "access comments" permission when searching for comments

The module doesn't sufficiently check the user's permissions when comments are searched.

This vulnerability is mitigated by the fact that it only occurs in specific site configurations:

  • A search index with item type "Comment".
  • Using the "Access check" data alteration for protection.
  • The site allowing certain users to view content (nodes), but not comments.
  • A search page for the comment index must be accessible for these users.

CVE identifier(s) issued

  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

  • Search API 7.x-1.x versions prior to 7.x-1.18.

Drupal core is not affected. If you do not use the contributed Search API module, there is nothing you need to do.

Solution

Install the latest version:

Also see the Search API project page.

Reported by

Fixed by

Coordinated by

  • Mike Potter 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 https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity