- Security-news - lists.drupal.org

Oauth - Critical - Unsupported - SA-CONTRIB-2017-006
by security-news＠drupal.org 25 Jan '17

25 Jan '17

View online: https://www.drupal.org/node/2846787 * Advisory ID: DRUPAL-SA-CONTRIB-2017-006 * Project: oauth [1] (third-party module) * Version: 7.x * Date: 2017-Jan-25 * Security risk: 19/25 ( Critical) AC:None/A:None/CI:Some/II:Some/E:Proof/TD:All [2] -------- DESCRIPTION --------------------------------------------------------- This module implements the OAuth 1.0 standard for use with Drupal and acts as a support module for other modules that wish to use OAuth. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * All versions Drupal core is not affected. If you do not use the contributed Oauth [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the oauth module for Drupal 7.x you should uninstall it. Also see the oauth [5] project page. -------- REPORTED BY --------------------------------------------------------- * Tim Brandin [6] * Damien McKenna [7] 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 [8]. Learn more about the Drupal Security team and their policies [9], writing secure code for Drupal [10], and securing your site [11]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [12] [1] https://www.drupal.org/project/oauth [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/oauth [5] https://www.drupal.org/project/oauth [6] https://www.drupal.org/u/timbrandin [7] https://www.drupal.org/u/DamienMcKenna [8] https://www.drupal.org/contact [9] https://www.drupal.org/security-team [10] https://www.drupal.org/writing-secure-code [11] https://www.drupal.org/security/secure-configuration [12] https://twitter.com/drupalsecurity

1 0

Mailjet - Highly critical - Arbitrary PHP code execution - SA-CONTRIB-2017-005
by security-news＠drupal.org 11 Jan '17

11 Jan '17

View online: https://www.drupal.org/node/2842760 * Advisory ID: DRUPAL-SA-CONTRIB-2017-005 * Project: (third-party module) * Version: 7.x * Date: 2017-January-11 * Security risk: 23/25 ( Highly Critical) AC:None/A:User/CI:All/II:All/E:Exploit/TD:All [1] * Vulnerability: Arbitrary PHP code execution -------- DESCRIPTION --------------------------------------------------------- The Mailjet module integrates with a 3rd party system to deliver site-generated emails, including newsletters, system notifications, etc. The Mailjet module included v5.2.8 of the PHPMailer library in its "includes" directory. Per PSA-2016-004 [2], this version of the PHPMailer library was vulnerable to PHP code execution. Per Drupal.org policy, 3rd party code should not be stored [3] in drupal.org repositories. Updating this module will require manual actions to replace the PHPMailer library as described in the README.txt file included in the release. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [4] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Mailjet 7.x-2.x versions prior 7.x-2.9. Drupal core is not affected. If you do not use the contributed module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Mailjet module for Drupal 7.x, upgrade to Mailjet7.x-2.9 [5] Also see the project page. -------- REPORTED BY --------------------------------------------------------- * hargobind [6] -------- FIXED BY ------------------------------------------------------------ * Proxiad [7] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Damien McKenna [8] 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 [9]. Learn more about the Drupal Security team and their policies [10], writing secure code for Drupal [11], and securing your site [12]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [13] [1] https://www.drupal.org/security-team/risk-levels [2] https://www.drupal.org/psa-2016-004 [3] https://www.drupal.org/node/422996 [4] http://cve.mitre.org/ [5] https://www.drupal.org/project/mailjet/releases/7.x-2.9 [6] https://www.drupal.org/u/hargobind [7] https://www.drupal.org/u/proxiad [8] https://www.drupal.org/u/damienmckenna [9] https://www.drupal.org/contact [10] https://www.drupal.org/security-team [11] https://www.drupal.org/writing-secure-code [12] https://www.drupal.org/security/secure-configuration [13] https://twitter.com/drupalsecurity

1 0

OpenLucius - Moderately Critical - Multiple vulnerabilities - SA-CONTRIB-2017-004
by security-news＠drupal.org 11 Jan '17

11 Jan '17

View online: https://www.drupal.org/node/2842759 * Advisory ID: DRUPAL-SA-CONTRIB-2017-004 * Project: OpenLucius [1] (third-party distribution) * Version: 7.x * Date: 2017-January-11 * Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting, Cross Site Request Forgery -------- DESCRIPTION --------------------------------------------------------- OpenLucius is a work management platform for social communication, documentation, and projects. The distribution doesn't sufficiently use tokens when marking messages for users as read thereby exposing a Cross Site Request Forgery (CSRF) vulnerability. The distribution does not sufficiently filter taxonomy term names before outputting them to HTML thereby exposing a Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have permissions to insert malicious taxonomy terms. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Openlucius 7.x-1.x versions prior to 7.x-1.6. Drupal core is not affected. If you do not use the contributed OpenLucius News [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Openlucius for Drupal 7.x, upgrade to Openlucius 7.x-1.7 [5] Also see the OpenLucius News [6] project page. -------- REPORTED BY --------------------------------------------------------- * Klaus Purer [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Thomas Dik [8] the distribution maintainer -------- COORDINATED BY ------------------------------------------------------ * Klaus Purer [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/openlucius [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/openlucius_news [5] https://www.drupal.org/project/openlucius/releases/7.x-1.7 [6] https://www.drupal.org/project/openlucius_news [7] https://www.drupal.org/user/262198 [8] https://www.drupal.org/user/1718070 [9] https://www.drupal.org/user/262198 [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

1 0

Autocomplete Deluxe - Moderately Critical - Cross Site Scripting (XSS) - SA-CONTRIB-2017-003
by security-news＠drupal.org 11 Jan '17

11 Jan '17

View online: https://www.drupal.org/node/2842730 * Advisory ID: DRUPAL-SA-CONTRIB-2017-003 * Project: Autocomplete Deluxe [1] (third-party module) * Version: 7.x * Date: 2017-January-11 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module creates a new widget for taxonomy fields based on JQuery UI autocomplete. The module doesn't sufficiently escape the entered taxonomy terms thereby exposing a Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have the permission to edit a taxonomy field. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Autocomplete Deluxe 7.x-2.x versions prior to 7.x-2.2. Drupal core is not affected. If you do not use the contributed Autocomplete Deluxe [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the autocomplete deluxe module for Drupal 7.x, upgrade to Autocomplete Deluxe 7.x-2.2 [5] Also see the Autocomplete Deluxe [6] project page. -------- REPORTED BY --------------------------------------------------------- * René Wolf [7] -------- FIXED BY ------------------------------------------------------------ * Sebastian Gilits [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Klaus Purer [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/autocomplete_deluxe [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/autocomplete_deluxe [5] https://www.drupal.org/project/autocomplete_deluxe/releases/7.x-2.2 [6] https://www.drupal.org/project/autocomplete_deluxe [7] https://www.drupal.org/user/927032 [8] https://www.drupal.org/user/512828 [9] https://www.drupal.org/user/262198 [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

1 0

Doubleclick for Publishers (DFP) - Moderately Critical - Multiple vulnerabilities - SA-CONTRIB-2017-002
by security-news＠drupal.org 04 Jan '17

04 Jan '17

View online: https://www.drupal.org/node/2841114 * Advisory ID: DRUPAL-SA-CONTRIB-2017-002 * Project: Doubleclick for Publishers (DFP) [1] (third-party module) * Version: 7.x * Date: 2017-January-04 * Security risk: 10/25 ( Moderately Critical) AC:Complex/A:User/CI:None/II:None/E:Exploit/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module enables you to to place advertisements on your site that are served by Google's DFP (Doubleclick for Publisher) service. The module has multiple Cross Site Scripting (XSS) vulnerabilities due to not sufficiently escaped fields. These vulnerabilities are mitigated by the fact that an attacker must have a role with the permission "administer DFP". The "administer DFP" permission is not marked as restricted. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * DFP 7.x-1.x versions prior to 7.x-1.5. Drupal core is not affected. If you do not use the contributed Doubleclick for Publishers (DFP) [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the DFP module for Drupal 7.x, upgrade to Doubleclick for Publishers (DFP) 7.x-1.5 [5] Also see the Doubleclick for Publishers (DFP) [6] project page. -------- REPORTED BY --------------------------------------------------------- * Alex Pott [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Alex Pott [8] of the Drupal Security Team * Alexander Ross (bleen) [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Michael Hess [10] of the Drupal Security Team * Lee Rowlands [11] of the Drupal Security Team * Cash Williams [12] 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 [13]. Learn more about the Drupal Security team and their policies [14], writing secure code for Drupal [15], and securing your site [16]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [17] [1] https://www.drupal.org/project/dfp [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/dfp [5] https://www.drupal.org/project/dfp/releases/7.x-1.5 [6] https://www.drupal.org/project/dfp [7] https://www.drupal.org/u/alexpott [8] https://www.drupal.org/u/alexpott [9] https://www.drupal.org/user/77375 [10] https://www.drupal.org/u/mlhess [11] https://www.drupal.org/user/395439 [12] https://www.drupal.org/u/cashwilliams [13] https://www.drupal.org/contact [14] https://www.drupal.org/security-team [15] https://www.drupal.org/writing-secure-code [16] https://www.drupal.org/security/secure-configuration [17] https://twitter.com/drupalsecurity

1 0

Permissions by Term -- Critical - Multiple vulnerabilities - SA-CONTRIB-2017-001
by security-news＠drupal.org 04 Jan '17

04 Jan '17

View online: https://www.drupal.org/node/2841094 * Advisory ID: DRUPAL-SA-CONTRIB-2017-001 * Project: Permissions by Term [1] (third-party module) * Version: 8.x * Date: 2017-January-04 * Security risk: 15/25 ( Critical) AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:All [2] * Vulnerability: Access bypass, Information Disclosure -------- DESCRIPTION --------------------------------------------------------- The Permissions by Term module extends Drupal functionality by restricting access to single nodes via taxonomy terms. Taxonomy terms are part of the Drupal core functionality. Taxonomy term permissions can be coupled to specific user accounts and/or user roles. Enabling the module unintentionally gives access to all unpublished nodes to anonymous users -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Permissions by Term 8.x-1.x versions prior to 8.x-1.11. Drupal core is not affected. If you do not use the contributed Permissions by Term [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Permissions by Term module for Drupal 8.x, upgrade to Permissions by Term 8.x-1.11. [5] Also see the Permissions by Term [6] project page. -------- REPORTED BY --------------------------------------------------------- * cedric_a [7] -------- FIXED BY ------------------------------------------------------------ * Peter Majmesku (jepSter) [8] - the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Michael Hess [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/permissions_by_term [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/permissions_by_term [5] https://www.drupal.org/project/permissions_by_term/releases/8.x-1.11 [6] https://www.drupal.org/project/permissions_by_term [7] https://www.drupal.org/u/cedric_a [8] https://www.drupal.org/u/jepster [9] https://www.drupal.org/u/mlhess [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

1 0

PHPmailer 3rd party library -- DRUPAL-SA-PSA-2016-004
by security-news＠drupal.org 26 Dec '16

26 Dec '16

View online: https://www.drupal.org/node/2839366 * Advisory ID: DRUPAL-SA-PSA-2016-004 * Project: PHPMailer [1] (third-party library) * Version: 7.x, 8.x * Date: 2016-December-26 * Security risk: 23/25 ( Highly Critical) AC:None/A:User/CI:All/II:All/E:Exploit/TD:All [2] * Vulnerability: Arbitrary PHP code execution -------- DESCRIPTION --------------------------------------------------------- The PHPMailer and SMTP modules (and maybe others) add support for sending e-mails using the 3rd party PHPMailer library. In general the Drupal project does not create advisories for 3rd party libraries. Drupal site maintainers should pay attention to the notifications provided by those 3rd party libraries as outlined in PSA-2011-002 - External libraries and plugins [3]. However, given the extreme criticality of this issue and the timing of its release we are issuing a Public Service Announcement to alert potentially affected Drupal site maintainers. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * CVE-2016-10033 -------- VERSIONS AFFECTED --------------------------------------------------- All versions of the external PHPMailer library < 5.2.18. Drupal core is not affected. If you do not use the contributed PHPMailer [4] third party library, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Upgrade to the newest version of the phpmailler library. https://github.com/PHPMailer/PHPMailer [5] -------- IF YOU ARE USING THE SMTP MODULE [6] -------------------------------- The SMTP module has a modified third party PHPMailer library in its codebase. The modified version of the library is not affected. A special thanks to Fabiano Sant'Ana [7], SMTP module [8] maintainer, for working on this with short notice. -------- REPORTED BY --------------------------------------------------------- * Dawid Golunski -------- 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 [9]. Learn more about the Drupal Security team and their policies [10], writing secure code for Drupal [11], and securing your site [12]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [13] [1] https://github.com/PHPMailer/PHPMailer [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/node/1189632 [4] https://github.com/PHPMailer/PHPMailer [5] https://github.com/PHPMailer/PHPMailer [6] https://www.drupal.org/project/smtp [7] https://www.drupal.org/u/wundo [8] https://www.drupal.org/project/smtp [9] https://www.drupal.org/contact [10] https://www.drupal.org/security-team [11] https://www.drupal.org/writing-secure-code [12] https://www.drupal.org/security/secure-configuration [13] https://twitter.com/drupalsecurity

1 0

High-performance JavaScript callback handler - Highly Critical - Multiple vulnerabilities - SA-CONTRIB-2016-063
by security-news＠drupal.org 07 Dec '16

07 Dec '16

View online: https://www.drupal.org/node/2833790 * Advisory ID: DRUPAL-SA-CONTRIB-2016-063 * Project: High-performance JavaScript callback handler [1] (third-party module) * Version: 7.x * Date: 2016-December-07 * Security risk: 22/25 ( Highly Critical) AC:None/A:None/CI:All/II:All/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting, Access bypass, Cross Site Request Forgery, Open Redirect, Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- The High-performance JavaScript callback handler module is a light weight callback to bypass most, if not all, of Drupal's bootstrapping process to achieve improved performance. The module does not sufficiently check whether or not a callback is being properly accessed or filtering for potential XSS or CSRF exploits. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * High-performance JavaScript callback handler (js) 7.x-1.x versions prior to 7.x-2.1. Drupal core is not affected. If you do not use the contributed High-performance JavaScript callback handler [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the js module for Drupal 7.x, upgrade to js 7.x-2.1 [5] *Note:* this upgrade is not backwards compatible with 7.x-1.x. Existing contrib and custom module implementations of this API will either need to be upgraded, replaced or removed. Also see the High-performance JavaScript callback handler [6] project page. -------- REPORTED BY --------------------------------------------------------- * Anthony Leach (anthonyleach) [7] -------- FIXED BY ------------------------------------------------------------ * Mark Carver (markcarver) [8] - module maintainer -------- COORDINATED BY ------------------------------------------------------ * Michael Hess [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/js [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/js [5] https://www.drupal.org/project/js/releases/7.x-2.1 [6] https://www.drupal.org/project/js [7] https://www.drupal.org/u/anthonyleach [8] https://www.drupal.org/u/markcarver [9] https://www.drupal.org/u/mlhess [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

1 0

Elysia Cron - Critical - Arbitrary PHP code execution - SA-CONTRIB-2016-062
by security-news＠drupal.org 30 Nov '16

30 Nov '16

View online: https://www.drupal.org/node/2831900 * Advisory ID: DRUPAL-SA-CONTRIB-2016-062 * Project: Elysia Cron [1] (third-party module) * Version: 7.x * Date: 2016-November-30 * Security risk: 11/25 ( Moderately Critical) AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:Uncommon [2] * Vulnerability: Arbitrary PHP code execution -------- DESCRIPTION --------------------------------------------------------- This module enables you to manage cron jobs. The module allows users with the permission "Administer elysia cron" to execute arbitrary PHP code via cron. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "Administer elysia cron". This permission is not marked as "restricted". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Elysia cron 7.x-2.x versions prior to 7.x-2.4. Drupal core is not affected. If you do not use the contributed Elysia Cron [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Revoke the permission "Administer elysia cron" for untrusted users. Elysia cron 7.x-2.4 [5] and up will indicate that the permission is restricted. Also see the Elysia Cron [6] project page. -------- REPORTED BY --------------------------------------------------------- * Heine Deelstra [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Kiselev Dmitry [8] the module co-maintainer * David Snopek [9] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * David Snopek [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/elysia_cron [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/elysia_cron [5] https://www.drupal.org/project/elysia_cron/releases/7.x-2.4 [6] https://www.drupal.org/project/elysia_cron [7] https://www.drupal.org/user/17943 [8] https://www.drupal.org/user/1945174 [9] https://www.drupal.org/user/266527 [10] https://www.drupal.org/user/266527 [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

1 0

Drupal Core - Moderately Critical - Multiple Vulnerabilities - SA-CORE-2016-005
by security-news＠drupal.org 16 Nov '16

16 Nov '16

View online: https://www.drupal.org/SA-CORE-2016-005 * Advisory ID: DRUPAL-SA-CORE-2016-005 * Project: Drupal core [1] * Version: 7.x, 8.x * Date: 2016-November-16 * Security risk: 13/25 ( Moderately Critical) AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:Uncommon [2] * Vulnerability: Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- .... Inconsistent name for term access query (Less critical - Drupal 7 and Drupal 8) Drupal provides a mechanism to alter database SELECT queries before they are executed. Contributed and custom modules may use this mechanism to restrict access to certain entities by implementing hook_query_alter() or hook_query_TAG_alter() in order to add additional conditions. Queries can be distinguished by means of query tags. As the documentation on EntityFieldQuery::addTag() [3] suggests, access-tags on entity queries normally follow the form ENTITY_TYPE_access (e.g. node_access). However, the taxonomy module's access query tag predated this system and used term_access as the query tag instead of taxonomy_term_access. As a result, before this security release modules wishing to restrict access to taxonomy terms may have implemented an unsupported tag, or needed to look for both tags (term_access and taxonomy_term_access) in order to be compatible with queries generated both by Drupal core as well as those generated by contributed modules like Entity Reference. Otherwise information on taxonomy terms might have been disclosed to unprivileged users. .... Incorrect cache context on password reset page (Less critical - Drupal 8) The user password reset form does not specify a proper cache context, which can lead to cache poisoning and unwanted content on the page. .... Confirmation forms allow external URLs to be injected (Moderately critical - Drupal 7) Under certain circumstances, malicious users could construct a URL to a confirmation form that would trick users into being redirected to a 3rd party website after interacting with the form, thereby exposing the users to potential social engineering attacks. .... Denial of service via transliterate mechanism (Moderately critical - Drupal 8) A specially crafted URL can cause a denial of service via the transliterate mechanism. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [4] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Drupal core 7.x versions prior to 7.52 * Drupal core 8.x versions prior to 8.2.3 -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use Drupal 7.x, upgrade to Drupal core 7.52 [5] * If you use Drupal 8.x, upgrade to Drupal core 8.2.3 [6] Also see the Drupal core [7] project page. -------- REPORTED BY --------------------------------------------------------- Inconsistent name for term access query: * znerol [8] Incorrect cache context on password reset page: * Charlotte Bone [9] Confirmation forms allow external URLs to be injected: * jnicola [10] * Ezra Wolfe [11] Denial of service via transliterate mechanism: * Lee Rowlands [12] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ Inconsistent name for term access query: * znerol [13] * xjm [14] of the Drupal Security Team * David Rothstein [15] of the Drupal Security Team * Dave Reid [16] of the Drupal Security Team * Larry Garfield [17] Incorrect cache context on password reset page: * Chris McCafferty [18], provisional Drupal Security Team member * xjm [19] of the Drupal Security Team * Alex Pott [20] of the Drupal Security Team * Michael Hess [21] of the Drupal Security Team * Nathaniel Catchpole [22] of the Drupal Security Team Confirmation forms allow external URLs to be injected: * Peter Wolanin [23] of the Drupal Security Team * Alex Pott [24] of the Drupal Security Team * David Rothstein [25] of the Drupal Security Team Denial of service via transliterate mechanism: * Lee Rowlands [26] of the Drupal Security Team * Cathy Theys [27] of the Drupal Security Team * Alex Pott [28] of the Drupal Security Team * Peter Wolanin [29] of the Drupal Security Team * Daniel Wehner [30] * Nate Haug [31] * Heine Deelstra [32] 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 [33]. Learn more about the Drupal Security team and their policies [34], writing secure code for Drupal [35], and securing your site [36]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [37] [1] https://www.drupal.org/project/drupal [2] https://www.drupal.org/security-team/risk-levels [3] https://api.drupal.org/api/drupal/includes!entity.inc/function/EntityFieldQ… [4] http://cve.mitre.org/ [5] https://www.drupal.org/project/drupal/releases/7.52 [6] https://www.drupal.org/project/drupal/releases/8.2.3 [7] https://www.drupal.org/project/drupal [8] https://www.drupal.org/user/63999 [9] https://www.drupal.org/u/charlotteb [10] https://www.drupal.org/u/jnicola [11] https://www.drupal.org/u/ezraw [12] https://www.drupal.org/u/larowlan [13] https://www.drupal.org/user/63999 [14] https://www.drupal.org/user/65776 [15] https://www.drupal.org/u/David_Rothstein [16] https://www.drupal.org/u/dave-reid [17] https://www.drupal.org/u/Crell [18] https://www.drupal.org/u/cilefen [19] https://www.drupal.org/user/65776 [20] https://www.drupal.org/user/157725 [21] https://www.drupal.org/u/mlhess [22] https://www.drupal.org/u/catch [23] https://www.drupal.org/u/pwolanin [24] https://www.drupal.org/user/157725 [25] https://www.drupal.org/u/David_Rothstein [26] https://www.drupal.org/u/larowlan [27] https://www.drupal.org/u/yesct [28] https://www.drupal.org/user/157725 [29] https://www.drupal.org/u/pwolanin [30] https://www.drupal.org/u/dawehner [31] https://www.drupal.org/u/quicksketch [32] https://www.drupal.org/u/Heine [33] https://www.drupal.org/contact [34] https://www.drupal.org/security-team [35] https://www.drupal.org/writing-secure-code [36] https://www.drupal.org/security/secure-configuration [37] https://twitter.com/drupalsecurity

1 0