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.

According to its self-reported version number, the detected Drupal application is affected by multiple vulnerabilities :

 - A flaw exists in the views subsystem due to a failure to restrict access to the Ajax endpoint to only views configured to use Ajax. This is mitigated if you have access restrictions on the view. (CVE-2017-6923)

 - A flaw exists with REST API that allows users without the correct permission to post comments via REST that are approved even if the user does not have permission to post approved comments. (CVE-2017-6924)

 - A flaw exists in the entity access system that allows unwanted access to view, create, update, or delete entities. This only affects entities that do not use or do not have UUIDs, and entities that have different access restrictions on different revisions of the same entity. (CVE-2017-6925)

Note that the scanner has not tested for these issues but has instead relied only on the application's self-reported version number.

-     [8.3.7](https://www.drupal.org/project/drupal/releases/8     .3.7)

  - [SA-CORE-2017-004 (CVE-2017-6923, CVE-2017-6924,     CVE-2017-6925)](https://www.drupal.org/SA-CORE-2017-004)

  -     [8.3.6](https://www.drupal.org/project/drupal/releases/8     .3.6)

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

According to its self-reported version, the instance of Drupal running on the remote web server is 8.x prior to 8.3.7. It is, therefore, affected by multiple vulnerabilities :

  - A flaw exists in the views subsystem due to a failure to restrict     access to the Ajax endpoint to only views configured to use Ajax.
    This is mitigated if you have access restrictions on the view.
    (CVE-2017-6923)

  - A flaw exists with REST API that allows users without the correct     permission to post comments via REST that are approved even if the     user does not have permission to post approved comments.
    (CVE-2017-6924)

  - A flaw exists in the entity access system that allows unwanted     access to view, create, update, or delete entities. This only     affects entities that do not use or do not have UUIDs, and     entities that have different access restrictions on different     revisions of the same entity. (CVE-2017-6925)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Drupal Security Team :

CVE-2017-6923: Views - Access Bypass - Moderately Critical

CVE-2017-6924: REST API can bypass comment approval - Access Bypass - Moderately Critica

CVE-2017-6925: Entity access bypass for entities that do not have UUIDs or have protected revisions - Access Bypass - Critical

ID	Name	Product	Family	Severity
98560	Drupal 8.x < 8.3.7 Multiple Vulnerabilities	Web App Scanning	Component Vulnerability	critical
103103	Fedora 25 : drupal8 (2017-902970c18f)	Nessus	Fedora Local Security Checks	critical
103097	Fedora 26 : drupal8 (2017-0fbd57c134)	Nessus	Fedora Local Security Checks	critical
102714	Drupal 8.x < 8.3.7 Multiple Vulnerabilities (SA-CORE-2017-004)	Nessus	CGI abuses	critical
102615	FreeBSD : drupal -- Drupal Core - Multiple Vulnerabilities (473b6a9e-8493-11e7-b24b-6cf0497db129)	Nessus	FreeBSD Local Security Checks	critical

Detections

Analytics

CVE-2017-6923

medium

Tenable Plugins

critical

critical

critical

critical

critical