May 2019 - Security-news - lists.drupal.org

Universally Unique IDentifier - Moderately critical - Access bypass - SA-CONTRIB-2019-052
by security-news＠drupal.org 29 May '19

29 May '19

View online: https://www.drupal.org/sa-contrib-2019-052 Project: Universally Unique IDentifier [1] Date: 2019-May-29 Security risk: *Moderately critical* 14∕25 AC:Complex/A:User/CI:All/II:Some/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Description: This module provides an API for adding universally unique identifiers (UUID) to Drupal objects, most notably entities. The module has a privilege escalation vulnerability when it's used in combination with Services+REST server. This vulnerability is mitigated by the fact that an attacker must authenticate to the site, services module must be configured on the site and the user update resource enabled. Solution: Install the latest version: * If you use the Universally Unique IDentifier module for Drupal 7.x, upgrade to UUID 7.x-1.3 [3] Also see the Universally Unique IDentifier [4] project page. Reported By: * Gustavo Iñiguez Goia [5] Fixed By: * Manuel Garcia [6] * Samuel Mortenson [7] of the Drupal Security Team Coordinated By: * Samuel Mortenson [8] of the Drupal Security Team [1] https://www.drupal.org/project/uuid [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/uuid/releases/7.x-1.3 [4] https://www.drupal.org/project/uuid [5] https://www.drupal.org/user/3419891 [6] https://www.drupal.org/user/213194 [7] https://www.drupal.org/user/2582268 [8] https://www.drupal.org/user/2582268

1 0

TableField - Moderately critical - Access bypass and Cross Site Scripting - SA-CONTRIB-2019-051
by security-news＠drupal.org 29 May '19

29 May '19

View online: https://www.drupal.org/sa-contrib-2019-051 Project: TableField [1] Version: 7.x-3.x-dev7.x-2.x-dev Date: 2019-May-29 Security risk: *Moderately critical* 13∕25 AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2] Vulnerability: Access bypass and Cross Site Scripting Description: This module allows you to attach tabular data to an entity. *Access bypass* There's no access check for users with an "Export Tablefield Data as CSV". They can export data from unpublished nodes or otherwise inaccessible entities. This vulnerability is mitigated by the fact that an attacker must have a role with the permission 'Export Tablefield Data as CSV'. *XSS* When "Raw data (JSON or XML)" is used in the field's Display settings, it doesn't sanitize JSON output before passing it on to be rendered. This vulnerability is mitigated by the fact that an attacker must have a role with Edit permissions. Solution: Install the latest version: * If you use a Tablefield module version 7.x-2.x, upgrade to tablefield 7.x-3.5 [3]. * If you use a Tablefield module version 7.x-3.x, upgrade to tablefield 7.x-2.8 [4]. Also see the TableField [5] project page. Reported By: * Yonatan Offek [6] Fixed By: * Yonatan Offek [7] * Jen Lampton [8] * Martin Postma [9] Coordinated By: * Greg Knaddison [10] of the Drupal Security Team [1] https://www.drupal.org/project/tablefield [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/tablefield/releases/7.x-3.5 [4] https://www.drupal.org/project/tablefield/releases/7.x-2.8 [5] https://www.drupal.org/project/tablefield [6] https://www.drupal.org/user/194009 [7] https://www.drupal.org/user/194009 [8] https://www.drupal.org/user/85586 [9] https://www.drupal.org/user/210402 [10] https://www.drupal.org/user/36762

1 0

Menu Item Extras - Moderately critical - Cross Site Request Forgery - SA-CONTRIB-2019-050
by security-news＠drupal.org 22 May '19

22 May '19

View online: https://www.drupal.org/sa-contrib-2019-050 Project: Menu Item Extras [1] Date: 2019-May-22 Security risk: *Moderately critical* 10∕25 AC:Basic/A:User/CI:None/II:Some/E:Theoretical/TD:Default [2] Vulnerability: Cross Site Request Forgery Description: This module enables you to handle fields for Custom Menu Links. The module doesn't sufficiently check requests to one of the module controllers if the user has permission 'administer menu'. This vulnerability is mitigated by the fact that an attacker must have a role with the permission to create content. Solution: Install the latest version: * If you use the Menu Item Extras module for Drupal 8.x, upgrade to Menu Item Extras 8.x-2.5 [3] Reported By: * Graham Cole [4] Fixed By: * Andriy Khomych [5] * Graham Cole [6] * Mykhailo Gurei [7] * Oleh Vehera [8] Coordinated By: * Michael Hess [9]of the Drupal Security Team [1] https://www.drupal.org/project/menu_item_extras [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/menu_item_extras/releases/8.x-2.5 [4] https://www.drupal.org/user/364457 [5] https://www.drupal.org/user/3287133 [6] https://www.drupal.org/user/364457 [7] https://www.drupal.org/user/2752909 [8] https://www.drupal.org/user/3260314 [9] https://www.drupal.org/u/mlhess

1 0

Workflow - Moderately critical - Cross Site Scripting - SA-CONTRIB-2019-049
by security-news＠drupal.org 22 May '19

22 May '19

View online: https://www.drupal.org/sa-contrib-2019-049 Project: Workflow [1] Date: 2019-May-22 Security risk: *Moderately critical* 13∕25 AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2] Vulnerability: Cross Site Scripting Description: The Workflow module enables you to create arbitrary Workflows, and assign them to Entities. The module doesn't sufficiently escape HTML in the field settings leading to a Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer nodes" and "administer workflow". Solution: Install the latest version: * If you use the Workflow module for Drupal 7.x, upgrade to Workflow 7.x-2.12 [3] Reported By: * Roberto Mariani [4] Fixed By: * Roberto Mariani [5] * David Snopek [6] of the Drupal Security Team * John Voskuilen [7] * Sarah Hood [8] * Greg Knaddison [9] of the Drupal Security Team Coordinated By: * Michael Hess [10] of the Drupal Security Team [1] https://www.drupal.org/project/workflow [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/workflow/releases/7.x-2.12 [4] https://www.drupal.org/user/1135096 [5] https://www.drupal.org/user/1135096 [6] https://www.drupal.org/user/266527 [7] https://www.drupal.org/user/591042 [8] https://www.drupal.org/user/275249 [9] https://www.drupal.org/user/36762 [10] https://www.drupal.org/u/mlhess

1 0

Multiple Registration - Critical - Access bypass - SA-CONTRIB-2019-048
by security-news＠drupal.org 15 May '19

15 May '19

View online: https://www.drupal.org/sa-contrib-2019-048 Project: Multiple Registration [1] Date: 2019-May-15 Security risk: *Critical* 19∕25 AC:Basic/A:None/CI:All/II:All/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Description: This module enables you to use special routes for user registration with special roles and custom field sets defined for the role. The module doesn't sufficiently check which user roles can be registered under the scenario when the user tries to register the user with the administrator role. This vulnerability is mitigated on sites where account approval is required as the user starts as blocked but still gets the "Administrator" role. Solution: Install the latest version: * If you use the Multiple registration module for Drupal 8.x, upgrade to Multiple registration 8.x-2.8 [3] Reported By: * iswilson [4] Fixed By: * Yaroslav Samoylenko [5] * iswilson [6] * Cash Williams [7] of the Drupal Security Team Coordinated By: * Cash Williams [8] of the Drupal Security Team [1] https://www.drupal.org/project/multiple_registration [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/multiple_registration/releases/8.x-2.8 [4] https://www.drupal.org/user/415095 [5] https://www.drupal.org/user/3554629 [6] https://www.drupal.org/user/415095 [7] https://www.drupal.org/user/421070 [8] https://www.drupal.org/user/421070

1 0

Opigno forum - Less critical - Access bypass - SA-CONTRIB-2019-046
by security-news＠drupal.org 15 May '19

15 May '19

View online: https://www.drupal.org/sa-contrib-2019-046 Project: Opigno forum [1] Date: 2019-May-15 Security risk: *Less critical* 9∕25 AC:Basic/A:User/CI:Some/II:None/E:Theoretical/TD:Uncommon [2] Vulnerability: Access bypass Description: In certain circumstances it is possible that certain forum information is available to unprivileged users because the access check is done with node access instead of grants. This vulnerability is mitigated by the fact that the module itself does not disclose information but only if there are listings such as views where the site builder / developer has not taken this into account. Solution: Install the latest version: * If you use the opigno_forum module for Drupal 8.x, upgrade to opigno_forum 8.x-1.2 [3] Also see the Opigno forum [4] project page. Reported By: * Nathaniel Catchpole [5] of the Drupal Security Team Fixed By: * James Aparicio [6] * Nathaniel Catchpole [7] of the Drupal Security Team Coordinated By: * Nathaniel Catchpole [8] of the Drupal Security Team [1] https://www.drupal.org/project/opigno_forum [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/opigno_forum/releases/8.x-1.2 [4] https://www.drupal.org/project/opigno_forum [5] https://www.drupal.org/user/35733 [6] https://www.drupal.org/user/2547544 [7] https://www.drupal.org/user/35733 [8] https://www.drupal.org/user/35733

1 0

Opigno Learning path - Moderately critical - Access bypass - SA-CONTRIB-2019-047
by security-news＠drupal.org 15 May '19

15 May '19

View online: https://www.drupal.org/sa-contrib-2019-047 Project: Opigno Learning path [1] Date: 2019-May-15 Security risk: *Moderately critical* 10∕25 AC:Basic/A:User/CI:Some/II:None/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Description: In certain configuration cases, when a learning path is configured as semi-private, anonymous users are allowed to join a learning path when they should not. Solution: Install the latest version: * If you use the opigno learning path module for Drupal 8.x, upgrade to opigno_learning_path 8.x-1.4 [3] * If using the opigno lms distribution it is recommended to update the whole distribution to the latest version Opigno lms 8.x-1.5 [4] Also see the Opigno Learning path [5] project page. Reported By: * Nathaniel Catchpole [6] of the Drupal Security Team Fixed By: * James Aparicio [7] * Nathaniel Catchpole [8] of the Drupal Security Team Coordinated By: * Nathaniel Catchpole [9] of the Drupal Security Team [1] https://www.drupal.org/project/opigno_learning_path [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/opigno_learning_path/releases/8.x-1.4 [4] https://www.drupal.org/project/opigno_lms/releases/8.x-1.5 [5] https://www.drupal.org/project/opigno_learning_path [6] https://www.drupal.org/user/35733 [7] https://www.drupal.org/user/2547544 [8] https://www.drupal.org/user/35733 [9] https://www.drupal.org/user/35733

1 0

Drupal core - Moderately critical - Third-party libraries - SA-CORE-2019-007
by security-news＠drupal.org 08 May '19

08 May '19

View online: https://www.drupal.org/sa-core-2019-007 Project: Drupal core [1] Date: 2019-May-08 Security risk: *Moderately critical* 14∕25 AC:Complex/A:Admin/CI:All/II:All/E:Theoretical/TD:Uncommon [2] Vulnerability: Third-party libraries Description: This security release fixes third-party dependencies included in or required by Drupal core. As described in TYPO3-PSA-2019-007: By-passing protection of Phar Stream Wrapper Interceptor [3]: >In order to intercept file invocations like file_exists or stat on >compromised Phar archives the base name has to be determined and checked >before allowing to be handled by PHP Phar stream handling. [...] > >The current implementation is vulnerable to path traversal leading to >scenarios where the Phar archive to be assessed is not the actual >(compromised) file. > Solution: Install the latest version: * If you are using Drupal 8.7, update to Drupal 8.7.1 [4] * If you are using Drupal 8.6 or earlier, update to Drupal 8.6.16 [5]. * If you are using Drupal 7, update to Drupal 7.67 [6]. Versions of Drupal 8 prior to 8.6.x are end-of-life and do not receive security coverage. Also see the Drupal core [7] project page. Reported By: * Daniel Le Gall [8] Fixed By: * Jess [9] of the Drupal Security Team * Michael Hess [10] of the Drupal Security Team * Oliver Hader [11] * David Snopek [12] of the Drupal Security Team * Alex Pott [13] of the Drupal Security Team * Daniel Le Gall [14] * Tim Plunkett [15] [1] https://www.drupal.org/project/drupal [2] https://www.drupal.org/security-team/risk-levels [3] https://typo3.org/security/advisory/typo3-psa-2019-007/ [4] https://www.drupal.org/project/drupal/releases/8.7.1 [5] https://www.drupal.org/project/drupal/releases/8.6.16 [6] https://www.drupal.org/project/drupal/releases/7.67 [7] https://www.drupal.org/project/drupal [8] https://www.drupal.org/user/3606561 [9] https://www.drupal.org/user/65776 [10] https://www.drupal.org/user/102818 [11] https://www.drupal.org/user/3602633 [12] https://www.drupal.org/user/266527 [13] https://www.drupal.org/user/157725 [14] https://www.drupal.org/user/3606561 [15] https://www.drupal.org/user/241634

1 0

Drupal 7 and 8 release on May 8th, 2019 - DRUPAL-PSA-2019-05-07 - PSA-2019-2019-05-07
by security-news＠drupal.org 07 May '19

07 May '19

View online: https://www.drupal.org/psa-2019-05-07 Date: 2019-May-07 Vulnerability: Drupal 7 and 8 release on May 8th, 2019 - DRUPAL-PSA-2019-05-07 Description: The Drupal Security Team will be coordinating a security release for Drupal 7 and 8 this week on Wednesday, May 8th, 2019. *We are issuing this PSA in advance because according to the regular security release window schedule [1], May 8th would not typically be a core security window.* *This release is rated as moderately critical. * The Drupal 7 and 8 core release will be made between 16:00 – 21:00 UTC (noon – 5:00pm Eastern). May 8th also remains a normal security release window for contributed projects. [1] https://www.drupal.org/node/1173280

1 0