Drupal access bypass vulnerability
Drupal.org Drupal Core
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| drupal/core Packagist |
|
|
| drupal/drupal Packagist |
|
|
Drupal.org Drupal Core
| Product | Affected | Fixed in |
|---|---|---|
| drupal/core Packagist |
|
|
| drupal/drupal Packagist |
|
|
In Drupal versions 8.4.x versions before 8.4.5 when using node access controls with a multilingual site, Drupal marks the untranslated version of a node as the default fallback for access queries. This fallback is used for languages that do not yet have a translated version of the created node. This can result in an access bypass vulnerability. This issue is mitigated by the fact that it only applies to sites that a) use the Content Translation module; and b) use a node access module such as Domain Access which implement hook_node_access_records().
From the CVE record · drupal
Drupal Core 8.4.x before 8.4.5 can use an untranslated node as the fallback for access queries when a requested translation does not exist. This can bypass node access controls on multilingual sites that use both the Content Translation module and a node access module implementing hook_node_access_records().
Operators of Drupal Core sites using Packagist drupal/core or drupal/drupal versions >=8.4.0 and <8.4.5 should check their installations.