View online: https://www.drupal.org/SA-CORE-2017-004
Drupal 8.3.7 is a maintenance releases which contain fixes for security
vulnerabilities.
Download Drupal 8.3.7 [1]
*Updating your existing Drupal 8 sites is strongly recommended (see
instructions for Drupal 8 [2]).* This release fixes security issues only;
there are no new features nor non-security-related bug fixes in this release.
See the 8.3.7 release notes [3] for details on important changes and known
issues affecting this release. Read on for details of the security
vulnerabilities that were fixed in this release.
* Advisory ID: DRUPAL-SA-CORE-2017-004
* Project: Drupal core [4]
* Version: 8.x
* Date: 2017-Aug-16
* Security risk: 15/25 ( Critical)
AC:None/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [5]
* Multiple vulnerabilities
-------- DESCRIPTION
---------------------------------------------------------
.... Views - Access Bypass - Moderately Critical - Drupal 8 - CVE-2017-6923
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.
.... REST API can bypass comment approval - Access Bypass - Moderately
Critical - Drupal 8 - CVE-2017-6924
When using the REST API, users without the correct permission can post
comments via REST that are approved even if the user does not have permission
to post approved comments.
This issue only affects sites that have the RESTful Web Services (rest)
module enabled, the comment entity REST resource enabled, and where an
attacker can access a user account on the site with permissions to post
comments, or where anonymous users can post comments.
.... Entity access bypass for entities that do not have UUIDs or have
protected revisions - Access Bypass - Critical - Drupal 8 -
CVE-2017-6925
There is a vulnerability in the entity access system that could allow
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.
-------- VERSIONS AFFECTED
---------------------------------------------------
* Drupal core 8.x versions prior to 8.3.7 [6]
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use Drupal 8.x, upgrade to Drupal core 8.3.7 [7]
* Drupal 7 core is not affected, however, Drupal 7 Views is: see Views -
Moderately Critical - Access Bypass - DRUPAL-SA-CONTRIB-2017-068 [8] *
Also see the Drupal core [9] project page.
-------- REPORTED BY
---------------------------------------------------------
.... Views - Access Bypass
* Maxim Podorov [10]
.... REST API can bypass comment approval - Access Bypass
* Arshad [11]
.... Entity access bypass for entities that do not have UUIDs or protected
revisions - Access Bypass
* Miles Worthington [12]
-------- FIXED BY
------------------------------------------------------------
.... Views - Access Bypass
* Klaus Purer [13]
* Daniel Wehner [14]
* Michael Hess [15] of the Drupal Security Team
* Len Swaneveld [16]
* Wim Leers [17]
.... REST API can bypass comment approval - Access Bypass
* Daniel Wehner [18]
* Arshad [19]
* Lee Rowlands [20] of the Drupal Security Team
* Wim Leers [21]
* Sascha Grossenbacher [22]
.... Entity access bypass for entities that do not have UUIDs or protected
revisions - Access Bypass
* Andrei Mateescu [23]
* Peter Wolanin [24] of the Drupal Security Team
* Matthew Donadio [25]
* xjm [26] of the Drupal Security Team
* Sascha Grossenbacher [27]
-------- 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 [28].
Learn more about the Drupal Security team and their policies [29], writing
secure code for Drupal [30], and securing your site [31].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [32]
[1] http://ftp.drupal.org/files/projects/drupal-8.3.7.tar.gz
[2] https://www.drupal.org/node/2700999
[3] https://www.drupal.org/project/drupal/releases/8.3.7
[4] https://www.drupal.org/project/drupal
[5] https://www.drupal.org/security-team/risk-levels
[6] https://www.drupal.org/project/drupal/releases/8.3.7
[7] https://www.drupal.org/project/drupal/releases/8.3.7
[8] https://www.drupal.org/node/2902604
[9] https://www.drupal.org/project/drupal
[10] https://www.drupal.org/u/maximpodorov
[11] https://www.drupal.org/u/arshadcn
[12] https://www.drupal.org/u/milesw
[13] https://www.drupal.org/u/klausi
[14] https://www.drupal.org/u/dawehner
[15] https://www.drupal.org/u/mlhess
[16] https://www.drupal.org/user/690914
[17] https://www.drupal.org/user/99777
[18] https://www.drupal.org/u/dawehner
[19] https://www.drupal.org/u/arshadcn
[20] https://www.drupal.org/user/395439
[21] https://www.drupal.org/user/99777
[22] https://www.drupal.org/u/berdir
[23] https://www.drupal.org/u/amateescu
[24] https://www.drupal.org/u/pwolanin
[25] https://www.drupal.org/u/mpdonadio
[26] https://www.drupal.org/u/xjm
[27] https://www.drupal.org/u/berdir
[28] https://www.drupal.org/contact
[29] https://www.drupal.org/security-team
[30] https://www.drupal.org/writing-secure-code
[31] https://www.drupal.org/security/secure-configuration
[32] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2900966
* Advisory ID: DRUPAL-SA-CONTRIB-2014-0XX
* Project: Facebook Like Button [1] (third-party module)
* Version: 7.x
* Date: 2017-August-09
* Security risk: 13/25 ( Moderately Critical)
AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2]
* Vulnerability: Cross Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
This module provides a Facebook Like button on node pages and blocks.
The module does not sufficiently sanitize output when configured to use
custom css rules.
This vulnerability is mitigated by the fact that an attacker must have a role
with the permission "administer fblikebutton".
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Facebook Like Button 7.x-2.x versions prior to 7.x-2.6.
Drupal core is not affected. If you do not use the contributed Facebook Like
Button [4] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the fblikebutton module for Drupal 7.x, upgrade to Facebook
like button 7.x-2.6 [5]
Also see the Facebook Like Button [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Tatar Balazs Janos [7]
-------- FIXED BY
------------------------------------------------------------
* Tatar Balazs Janos [8]
* Getulio Sánchez [9] The module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Michael Hess [10] of the Drupal Security Team
* David Snopek [11] 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 [12].
Learn more about the Drupal Security team and their policies [13], writing
secure code for Drupal [14], and securing your site [15].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [16]
[1] https://www.drupal.org/project/fblikebutton
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/fblikebutton
[5] https://www.drupal.org/project/fblikebutton/releases/7.x-2.6
[6] https://www.drupal.org/project/fblikebutton
[7] https://www.drupal.org/u/tatarbj
[8] https://www.drupal.org/u/tatarbj
[9] https://www.drupal.org/user/3101285
[10] https://www.drupal.org/u/mlhess
[11] https://www.drupal.org/u/dsnopek
[12] https://www.drupal.org/contact
[13] https://www.drupal.org/security-team
[14] https://www.drupal.org/writing-secure-code
[15] https://www.drupal.org/security/secure-configuration
[16] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2900943
* Advisory ID: DRUPAL-SA-CONTRIB-2017-063
* Project: Relation [1] (third-party module)
* Version: 7.x
* Date: 2017-August-09
* Security risk: 14/25 ( Moderately Critical)
AC:None/A:User/CI:Some/II:None/E:Exploit/TD:Uncommon [2]
* Vulnerability: Access bypass
-------- DESCRIPTION
---------------------------------------------------------
This module enables you to store relationships between entities as fieldable
entities.
The module doesn't sufficiently check permissions when displaying related
entities labels with the Relation Dummy Field module widget.
This vulnerability is mitigated by the fact that the optional Relation Dummy
Field module must be enabled and any entity must be configured to display
related entities with the widget provided by the module.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Relation 7.x-1.x versions prior to 7.x-1.1.
Drupal core is not affected. If you do not use the contributed Relation [4]
module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Relation module for Drupal 7.x, upgrade to Relation
7.x-1.1
[5]
Also see the Relation [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Lars Schröter [7]
-------- FIXED BY
------------------------------------------------------------
* Mikko Rantanen [8] the module maintainer
* Lars Schröter [9]
-------- COORDINATED BY
------------------------------------------------------
* Michael Hess [10] 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 [11].
Learn more about the Drupal Security team and their policies [12], writing
secure code for Drupal [13], and securing your site [14].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [15]
[1] https://www.drupal.org/project/relation
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/relation
[5] https://www.drupal.org/project/relation/releases/7.x-1.1
[6] https://www.drupal.org/project/relation
[7] https://www.drupal.org/user/115856
[8] https://www.drupal.org/u/mikran
[9] https://www.drupal.org/user/115856
[10] https://www.drupal.org/u/mlhess
[11] https://www.drupal.org/contact
[12] https://www.drupal.org/security-team
[13] https://www.drupal.org/writing-secure-code
[14] https://www.drupal.org/security/secure-configuration
[15] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2899342
* Advisory ID: DRUPAL-SA-CONTRIB-2017-061
* Project: ajax_facets [1] (third-party module)
* Date: 2-Aug-2017
-------- DESCRIPTION
---------------------------------------------------------
This module allows you to create facet filters which working by AJAX. Filters
and search results will be updated by AJAX.
The security team is marking this module unsupported. There is a known
security issue with the module that has not been fixed by the maintainer. If
you would like to maintain this module, please read:
https://www.drupal.org/node/251466
-------- VERSIONS AFFECTED
---------------------------------------------------
* All versions
Drupal core is not affected. If you do not use the contributed ajax_facets
[2] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
If you use the ajax_facets module for Drupal you should uninstall it.
Also see the ajax_facets [3] project page.
-------- REPORTED BY
---------------------------------------------------------
* Frédéric G. Marand [4]
-------- FIXED BY
------------------------------------------------------------
Not applicable
-------- 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 [5].
Learn more about the Drupal Security team and their policies [6], writing
secure code for Drupal [7], and securing your site [8].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [9]
[1] https://www.drupal.org/project/ajax_facets
[2] https://www.drupal.org/project/ajax_facets
[3] https://www.drupal.org/project/ajax_facets
[4] https://www.drupal.org/user/27985
[5] https://www.drupal.org/contact
[6] https://www.drupal.org/security-team
[7] https://www.drupal.org/writing-secure-code
[8] https://www.drupal.org/security/secure-configuration
[9] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2899340
* Advisory ID: DRUPAL-SA-CONTRIB-2017-059
* Project: html_title [1] (third-party module)
* Date: 2-Aug-2017
-------- DESCRIPTION
---------------------------------------------------------
The HTML Title module allows a limited set of HTML markup (em, sub, sup, b,
i, strong, cite, code, bdi, wbr) to be used in node titles.
The security team is marking this module unsupported. There is a known
security issue with the module that has not been fixed by the maintainer. If
you would like to maintain this module, please read:
https://www.drupal.org/node/251466
-------- VERSIONS AFFECTED
---------------------------------------------------
* All versions
Drupal core is not affected. If you do not use the contributed html_title [2]
module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
If you use the html_title module for Drupal you should uninstall it.
Also see the html_title [3] project page.
-------- REPORTED BY
---------------------------------------------------------
* Nathaniel Catchpole [4] of the Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
Not applicable
-------- 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 [5].
Learn more about the Drupal Security team and their policies [6], writing
secure code for Drupal [7], and securing your site [8].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [9]
[1] https://www.drupal.org/project/html_title
[2] https://www.drupal.org/project/html_title
[3] https://www.drupal.org/project/html_title
[4] https://www.drupal.org/u/catch
[5] https://www.drupal.org/contact
[6] https://www.drupal.org/security-team
[7] https://www.drupal.org/writing-secure-code
[8] https://www.drupal.org/security/secure-configuration
[9] https://twitter.com/drupalsecurity