View online: https://www.drupal.org/node/2554145
* Advisory ID: DRUPAL-SA-CONTRIB-2015-141
* Project: Chaos tool suite (ctools) [1] (third-party module)
* Version: 6.x, 7.x
* Date: 2015-August-19
* Security risk: 14/25 ( Moderately Critical)
AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2]
* Vulnerability: Cross Site Scripting, Access bypass, Multiple
vulnerabilities
-------- DESCRIPTION
---------------------------------------------------------
.... Cross Site Scripting (XSS)
Ctools in Drupal 6 provides a number of APIs and extensions for Drupal, and
is a dependency for many of the most popular modules, including Views, Panels
and Entityreference. Many features introduced in Drupal Core once lived in
ctools.
This vulnerability can be mitigated by the fact that ctools must load its
javascript on the page and the user has access to submit data through a form
(such as a comment or node) that allows 'a' tags.
This patch is a backport for SA-CORE-2015-003 [3].
.... Access bypass
This module provides a number of APIs and extensions for Drupal, and is a
dependency for many of the most popular modules, including Views, Panels and
Features.
The module doesn't sufficiently verify the "edit" permission for the "content
type" plugins that are used on Panels and similar systems to place content
and functionality on a page.
This vulnerability is mitigated by the fact that the user must have access to
edit a display via a Panels display system, e.g. via Panels pages, Mini
Panels, Panel Nodes, Panelizer displays, IPE, Panels Everywhere, etc.
Furthermore, either a contributed module provides a CTools content type
plugin, or a custom plugin must be written that inherits permissions from
another plugin and must have a different permission defined; if no "edit"
permission is set up for the child object CTools did not check the
permissions of the parent object. One potential scenario would allow people
who did not have edit access to Fieldable Panels Panes panes, which were
specifically set to not be reusable, to edit them despite the person's lack
of access.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [4] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
Cross Site Scripting:
* ctools 6.x-1.x versions prior to 6.x-1.14.
Access bypass:
* ctools 6.x-1.x versions prior to 6.x-1.14.
* ctools 7.x-1.x versions prior to 7.x-1.8.
Drupal core is not affected. If you do not use the contributed Chaos tool
suite (ctools) [5] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the ctools module for Drupal 6.x, upgrade to ctools 6.x-1.14
[6]
* If you use the ctools module for Drupal 7.x, upgrade to ctools 7.x-1.8
[7]
Also see the Chaos tool suite (ctools) [8] project page.
-------- REPORTED BY
---------------------------------------------------------
Cross Site Scripting:
* Peter Wolanin [9] of the Drupal Security Team
Access bypass:
* Andor Dávid [10]
-------- FIXED BY
------------------------------------------------------------
Cross Site Scripting:
* James Gilliland [11] of the Drupal Security Team
* Alex Bronstein [12], Drupal core patch coordinator
* Kris Vanderwater [13] the module maintainer
* Jakob Perry [14] the module maintainer
Access bypass:
* Andor Dávid [15]
* Damien McKenna [16], provisional member of the Drupal Security Team
* Michael Miles [17] of the Drupal Security Team
* Jakob Perry [18] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Pere Orga [19] 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 [20].
Learn more about the Drupal Security team and their policies [21], writing
secure code for Drupal [22], and securing your site [23].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [24]
[1] https://www.drupal.org/project/ctools
[2] https://www.drupal.org/security-team/risk-levels
[3] https://www.drupal.org/SA-CORE-2015-003
[4] http://cve.mitre.org/
[5] https://www.drupal.org/project/ctools
[6] https://www.drupal.org/node/2554133
[7] https://www.drupal.org/node/2554141
[8] https://www.drupal.org/project/ctools
[9] https://www.drupal.org/u/pwolanin
[10] https://www.drupal.org/u/sweetchuck
[11] https://www.drupal.org/u/neclimdul
[12] https://www.drupal.org/user/78040
[13] https://www.drupal.org/user/61203
[14] https://www.drupal.org/user/45640
[15] https://www.drupal.org/u/sweetchuck
[16] https://www.drupal.org/u/damienmckenna
[17] https://www.drupal.org/u/mikemiles86
[18] https://www.drupal.org/u/japerry
[19] https://www.drupal.org/user/2301194
[20] https://www.drupal.org/contact
[21] https://www.drupal.org/security-team
[22] https://www.drupal.org/writing-secure-code
[23] https://www.drupal.org/security/secure-configuration
[24] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2553977
* Advisory ID: DRUPAL-SA-CONTRIB-2015-140
* Project: Search API Autocomplete [1] (third-party module)
* Version: 7.x
* Date: 2015-August-19
* Security risk: 6/25 ( Less Critical)
AC:Complex/A:User/CI:None/II:None/E:Theoretical/TD:Default [2]
* Vulnerability: Cross Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
This module enables you to add autocomplete suggestions for search forms
created with the Search API module [3].
The module doesn't sufficiently sanitize the HTML output for the returned
suggestions, theoretically allowing an attacker to include custom HTML there.
This vulnerability is mitigated by the fact that an attacker must have a role
with the permission to create new content (or other indexed entities) and
that the search index must be configured to use the HTML filter processor.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [4] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Search API Autocomplete 7.x-1.x versions prior to 7.x-1.3.
Drupal core is not affected. If you do not use the contributed Search API
Autocomplete [5] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Search API Autocomplete module for Drupal 7.x, upgrade to
Search API Autocomplete 7.x-1.3 [6]
Also see the Search API Autocomplete [7] project page.
-------- REPORTED BY
---------------------------------------------------------
* Thomas Seidl [8] the module maintainer
-------- FIXED BY
------------------------------------------------------------
* Thomas Seidl [9] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Klaus Purer [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/search_api_autocomplete
[2] https://www.drupal.org/security-team/risk-levels
[3] https://www.drupal.org/project/search_api
[4] http://cve.mitre.org/
[5] https://www.drupal.org/project/search_api_autocomplete
[6] https://www.drupal.org/node/2553485
[7] https://www.drupal.org/project/search_api_autocomplete
[8] https://www.drupal.org/u/drunken-monkey
[9] https://www.drupal.org/u/drunken-monkey
[10] https://www.drupal.org/u/klausi
[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/2553971
* Advisory ID: DRUPAL-SA-CONTRIB-2015-139
* Project: Workbench Email [1] (third-party module)
* Version: 7.x
* Date: 2015-August-19
* Security risk: 10/25 ( Moderately Critical)
AC:Basic/A:User/CI:None/II:Some/E:Theoretical/TD:Default [2]
* Vulnerability: Access bypass
-------- DESCRIPTION
---------------------------------------------------------
Workbench Email module provides a way for administrators to define email
transitions and configurable email subject / messages between those
transitions.
The module causes node and field validations to be skipped when saving nodes.
The vulnerability is mitigated by the fact that an attacker must have a role
with permission to create or update nodes.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Workbench Email 7.x-3.x versions prior to 7.x-3.4
Drupal core is not affected. If you do not use the contributed Workbench
Email [4] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Workbench Email module for Drupal 7.x, upgrade to
Workbench
Email 7.x-3.4 [5]
Also see the Workbench Email [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Yves Chedemois [7]
-------- FIXED BY
------------------------------------------------------------
* Brandon Tate [8] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Pere orga [9] 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 [10].
Learn more about the Drupal Security team and their policies [11], writing
secure code for Drupal [12], and securing your site [13].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [14]
[1] https://www.drupal.org/project/workbench_email
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/workbench_email
[5] https://www.drupal.org/node/2484229
[6] https://www.drupal.org/project/workbench_email
[7] https://www.drupal.org/u/yched
[8] https://www.drupal.org/u/teknic
[9] https://www.drupal.org/u/pere-orga
[10] https://www.drupal.org/contact
[11] https://www.drupal.org/security-team
[12] https://www.drupal.org/writing-secure-code
[13] https://www.drupal.org/security/secure-configuration
[14] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2546174
* Advisory ID: DRUPAL-SA-CONTRIB-2015-138
* Project: Compass Rose [1] (third-party module)
* Version: 6.x
* Date: 2015-August-05
* Security risk: 17/25 ( Critical)
AC:None/A:None/CI:Some/II:Some/E:Theoretical/TD:Default [2]
* Vulnerability: Cross Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
Compass Rose module provides a type of CCK field that allows to represent the
most common orientations (North, North-East, East, South-East, South,
South-West, West and North-West).
The module was embedding a JavaScript library from an external source that
was not reliable, thereby exposing the site to a Cross Site Scripting (XSS)
vulnerability.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Compass Rose 6.x-1.x versions prior to 6.x-1.1.
Drupal core is not affected. If you do not use the contributed Compass Rose
[4] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Compass Rose module for Drupal 6.x, upgrade to Compass
Rose
6.x-1.1 [5]
Also see the Compass Rose [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Dean Flory [7]
-------- FIXED BY
------------------------------------------------------------
* Pablo López [8] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Pere Orga [9] 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 [10].
Learn more about the Drupal Security team and their policies [11], writing
secure code for Drupal [12], and securing your site [13].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [14]
[1] https://www.drupal.org/project/compass_rose
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/compass_rose
[5] https://www.drupal.org/node/2545132
[6] https://www.drupal.org/project/compass_rose
[7] https://www.drupal.org/user/811452
[8] https://www.drupal.org/u/plopesc
[9] https://www.drupal.org/user/2301194
[10] https://www.drupal.org/contact
[11] https://www.drupal.org/security-team
[12] https://www.drupal.org/writing-secure-code
[13] https://www.drupal.org/security/secure-configuration
[14] https://twitter.com/drupalsecurity
View online: https://www.drupal.org/node/2546164
* Advisory ID: DRUPAL-SA-CONTRIB-2015-137
* Project: Quick Edit [1] (third-party module)
* Version: 7.x
* Date: 2015-August-05
* Security risk: 14/25 ( Moderately Critical)
AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2]
* Vulnerability: Cross Site Scripting, Multiple vulnerabilities
-------- DESCRIPTION
---------------------------------------------------------
This module enables you to in-place edit entities' fields.
The module doesn't sufficiently filter entity titles under the scenario where
the user starts in-place editing an entity. The module also doesn't
sufficiently filter node titles under the scenario where a node is displayed
(albeit only on pages that are not the node page, so e.g. Views listings).
This vulnerability is mitigated by the fact that an attacker must have a role
with the permission to create or edit node entities (e.g. page, article …).
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Quick Edit 7.x-1.x versions prior to 7.x-1.2.
Drupal core is not affected. If you do not use the contributed Quick Edit [4]
module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Quick Edit module for Drupal 7.x, upgrade to Quick Edit
7.x-1.2 [5]
Also see the Quick Edit [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Joris van Eijden [7]
-------- FIXED BY
------------------------------------------------------------
* Wim Leers [8] the module maintainer
* Théodore Biadala [9] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Pere Orga [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/quickedit
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/quickedit
[5] https://www.drupal.org/node/2546066
[6] https://www.drupal.org/project/quickedit
[7] https://www.drupal.org/u/JvE
[8] https://www.drupal.org/u/wim-leers
[9] https://www.drupal.org/u/nod_
[10] https://www.drupal.org/user/2301194
[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/2542380
* Advisory ID: DRUPAL-SA-CONTRIB-2014-0XX
* Project: Commerce Commonwealth (CBA) [1] (third-party module)
* Version: 7.x
* Date: 2015-August-05
* Security risk: 12/25 ( Moderately Critical)
AC:Complex/A:None/CI:None/II:Some/E:Theoretical/TD:All [2]
* Vulnerability: Multiple vulnerabilities
-------- DESCRIPTION
---------------------------------------------------------
This module enables you to pay for items on Drupal Commerce, using Commerce
Commonwealth payment gateway.
The module doesn't sufficiently validate the payment under certain specific
scenarios. A malicious user can modify the urls used in gateway interaction
with Commbank to make a failed payment appear to be a successful payment.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Commerce Commonwealth (CBA) 7.x-1.x versions prior to 7.x-1.5.
Drupal core is not affected. If you do not use the contributed Commerce
Commonwealth (CBA) [4] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Commerce Commonwealth (CBA) module for Drupal 7.x, upgrade
to Commerce Commonwealth (CBA) 7.x-1.5 [5]
Also see the Commerce Commonwealth (CBA) [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Greg Knaddison [7] of the Drupal Security Team
* Michael Kandelaars [8]
* John Avery [9]
-------- FIXED BY
------------------------------------------------------------
* John Avery [10] the module maintainer
* Michael Kandelaars [11]
* Greg Knaddison [12] of the Drupal Security Team
-------- COORDINATED BY
------------------------------------------------------
* Greg Knaddison [13] 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 [14].
Learn more about the Drupal Security team and their policies [15], writing
secure code for Drupal [16], and securing your site [17].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [18]
[1] https://www.drupal.org/project/commerce_commonwealth
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/commerce_commonwealth
[5] https://www.drupal.org/node/2541832
[6] https://www.drupal.org/project/commerce_commonwealth
[7] https://www.drupal.org/user/36762
[8] https://www.drupal.org/user/2993501
[9] https://www.drupal.org/user/2573976
[10] https://www.drupal.org/user/2573976
[11] https://www.drupal.org/user/2993501
[12] https://www.drupal.org/user/36762
[13] https://www.drupal.org/user/36762
[14] https://www.drupal.org/contact
[15] https://www.drupal.org/security-team
[16] https://www.drupal.org/writing-secure-code
[17] https://www.drupal.org/security/secure-configuration
[18] https://twitter.com/drupalsecurity