View online: https://www.drupal.org/SA-CORE-2016-004
-------- DESCRIPTION
---------------------------------------------------------
Users who have rights to edit a node, can set the visibility on comments for
that node.
* Advisory ID: DRUPAL-SA-CORE-2016-004
* Project: Drupal core [1]
* Version:li 8.x
* Date: 2016-September-21
* Security risk: 18/25 ( Critical)
AC:Basic/A:User/CI:Some/II:Some/E:Proof/TD:Default [2]
* Vulnerability:
-------- DESCRIPTION
---------------------------------------------------------
*Users without "Administer comments" can set comment visibility on nodes they
can edit. (Less critical)*
Users who have rights to edit a node, can set the visibility on comments for
that node. This should be restricted to those who have the administer
comments permission.
*Cross-site Scripting in http exceptions (critical) *
An attacker could create a specially crafted url, which could execute
arbitrary code in the victim’s browser if loaded. Drupal was not properly
sanitizing an exception
*Full config export can be downloaded without administrative permissions
(critical) *
The system.temporary route would allow the download of a full config export.
The full config export should be limited to those with Export configuration
permission.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
8.x
-------- SOLUTION
------------------------------------------------------------
Upgrade to Drupal 8.1.10
-------- REPORTED BY
---------------------------------------------------------
*Users without "Administer comments" can set comment visibility on nodes they
can edit.*
* Quintus Maximus [4]
* Kier Heyl [5]
*XSS in http exceptions*
* Ivan [6]
*Full config export can be downloaded without administrative permissions *
* Anton Shubkin [7]
-------- FIXED BY
------------------------------------------------------------
*Users without "Administer comments" can set comment visibility on nodes they
can edit.*
* Lee Rowlands of the Drupal Security Team [8]
* Stefan Ruijsenaars of the Drupal Security Team [9]
* Andrey Postnikov [10]
* Daniel Wehner [11]
*XSS in http exceptions*
* xjm of the Drupal Security Team [12]
* Daniel Wehner [13]
* Alex Pott of the Drupal Security Team [14]
* Cash Williams of the Drupal Security Team [15]
* Pere Orga of the Drupal Security Team [16]
* David Snopek of the Drupal Security Team [17]
* Heine Deelstra of the Drupal Security Team
*Full config export can be downloaded without administrative permissions *
* Nathaniel Catchpole of the Drupal Security Team [18]
* Alex Pott of the Drupal Security Team [19]
* Anton Shubkin [20]
* xjm of the Drupal Security Team [21]
* Peter Wolanin of the Drupal Security Team [22]
-------- COORDINATED BY
------------------------------------------------------
The Drupal Security Team [23]
-------- 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 [24].
Learn more about the Drupal Security team and their policies [25], writing
secure code for Drupal [26], and securing your site [27].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [28]
[1] https://www.drupal.org/project/drupal
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] http://www.drupal.org/u/q2u
[5] https://www.drupal.org/u/kierheyl
[6] https://www.drupal.org/user/556138
[7] https://www.drupal.org/user/1060446
[8] http://www.drupal.org/u/larowlan
[9] https://www.drupal.org/u/stefanr-0
[10] https://www.drupal.org/user/118908
[11] https://www.drupal.org/user/99340
[12] https://www.drupal.org/user/65776
[13] https://www.drupal.org/user/99340
[14] https://www.drupal.org/user/157725
[15] https://www.drupal.org/user/421070
[16] https://www.drupal.org/u/pere-orga
[17] https://www.drupal.org/u/dsnopek
[18] https://www.drupal.org/u/catch
[19] https://www.drupal.org/user/157725
[20] https://www.drupal.org/user/1060446
[21] https://www.drupal.org/user/65776
[22] https://www.drupal.org/user/49851
[23] https://www.drupal.org/security-team
[24] https://www.drupal.org/contact
[25] https://www.drupal.org/security-team
[26] https://www.drupal.org/writing-secure-code
[27] https://www.drupal.org/security/secure-configuration
[28] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2796651
* Advisory ID: DRUPAL-SA-CONTRIB-2016-051
* Project: Flag Lists [1] (third-party module)
* Version: 7.x
* Date: 2016-September-07
* Security risk: 14/25 ( Moderately Critical)
AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2]
* Vulnerability: Cross Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
This module enables regular users to create unlimited private flags called
lists.
The flag_lists module doesn't sufficiently filter the output when applying
token strings to flag_lists links leading to a persistent Cross Site
Scripting (XSS) attack.
This vulnerability is mitigated by the fact that an attacker must have a role
with the "Create flag lists" permission.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* flag_lists 7.x-3.x versions prior to 7.x-3.1.
* flag_lists 7.x-1.x versions prior to 7.x-1.3.
Please note that there are two different versions available of the flag_lists
module. One 7.x-3.x which is used together with flag 7.x-3.x and one for the
earlier flag module prior to 7.x-3.x.
Drupal core is not affected. If you do not use the contributed Flag lists
module, there is nothing you need to do.
Drupal core is not affected. If you do not use the contributed Flag Lists [4]
module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the flag_lists module for Drupal 7.x-3.x, upgrade to Flag
Lists
7.x-3.1 [5]
* If you use the flag_lists module for Drupal 7.x-1.x, upgrade to Flag
Lists
7.x-1.3 [6]
Also see the Flag Lists [7] project page.
-------- REPORTED BY
---------------------------------------------------------
* Mike Madison [8]
-------- FIXED BY
------------------------------------------------------------
* Thomas Nilsson [9] the flag_lists module maintainer
* Joachim Noreiko [10] the flag module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Mike Potter [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/flag_lists
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/flag_lists
[5] https://www.drupal.org/project/flag_lists/releases/7.x-3.1
[6] https://www.drupal.org/project/flag_lists/releases/7.x-1.3
[7] https://www.drupal.org/project/flag_lists
[8] https://www.drupal.org/user/1232054
[9] https://www.drupal.org/user/15938
[10] https://www.drupal.org/user/107701
[11] https://www.drupal.org/user/616192
[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