Access bypass in Drupal 8 views
Drupal core
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| drupal/core Packagist |
|
|
| drupal/drupal Packagist |
|
|
Drupal core
| Product | Affected | Fixed in |
|---|---|---|
| drupal/core Packagist |
|
|
| drupal/drupal Packagist |
|
|
In Drupal 8.x prior to 8.3.7 When creating a view, you can optionally use Ajax to update the displayed data via filter parameters. The views subsystem/module did not restrict access to the Ajax endpoint to only views configured to use Ajax. This is mitigated if you have access restrictions on the view. It is best practice to always include some form of access restrictions on all views, even if you are using another module to display them.
From the CVE record · drupal
In Drupal 8.x before 8.3.7, the Views subsystem does not limit its Ajax endpoint to views configured to use Ajax. An attacker can access that endpoint for other views; access restrictions on a view mitigate the issue. The input does not specify whether authentication or user interaction is required.
Operators using Packagist drupal/core or drupal/drupal versions >=8.0 and <8.3.7 should check their installations.