December 2019 - Security-news

Drupal core - Moderately critical - Multiple vulnerabilities - SA-CORE-2019-010
by security-news＠drupal.org 18 Dec '19

18 Dec '19

View online: https://www.drupal.org/sa-core-2019-010 Project: Drupal core [1] Version: 8.8.x-dev8.7.x-dev Date: 2019-December-18 Security risk: *Moderately critical* 14∕25 AC:Basic/A:Admin/CI:Some/II:All/E:Theoretical/TD:Default [2] Vulnerability: Multiple vulnerabilities Description: Drupal 8 core's file_save_upload() function does not strip the leading and trailing dot ('.') from filenames, like Drupal 7 did. Users with the ability to upload files with any extension in conjunction with contributed modules may be able to use this to upload system files such as .htaccess in order to bypass protections afforded by Drupal's default .htaccess file. After this fix, file_save_upload() now trims leading and trailing dots from filenames. Solution: Install the latest version: * If you use Drupal core 8.7.x: 8.7.11 [3] * If you use Drupal core 8.8.x: 8.8.1 [4] Versions of Drupal 8 prior to 8.7.x are end-of-life and do not receive security coverage. Reported By: * Rohit Kapur [5] * Filipe Reis [6] * Dan Reif [7] * mramydnei [8] Fixed By: * Lee Rowlands [9] of the Drupal Security Team * Greg Knaddison [10] of the Drupal Security Team * Michael Hess [11] of the Drupal Security Team * Kim Pepper [12] * Alex Pott [13] of the Drupal Security Team * Derek Wright [14] * Jess [15] of the Drupal Security Team * David Rothstein [16] of the Drupal Security Team [1] https://www.drupal.org/project/drupal [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/drupal/releases/8.7.11 [4] https://www.drupal.org/project/drupal/releases/8.8.1 [5] https://www.drupal.org/user/3623849 [6] https://www.drupal.org/user/3521501 [7] https://www.drupal.org/user/454444 [8] https://www.drupal.org/user/3529990 [9] https://www.drupal.org/user/395439 [10] https://www.drupal.org/user/36762 [11] https://www.drupal.org/user/102818 [12] https://www.drupal.org/user/370574 [13] https://www.drupal.org/user/157725 [14] https://www.drupal.org/user/46549 [15] https://www.drupal.org/user/65776 [16] https://www.drupal.org/user/124982

1 0

Drupal core - Critical - Multiple vulnerabilities - SA-CORE-2019-012
by security-news＠drupal.org 18 Dec '19

18 Dec '19

View online: https://www.drupal.org/sa-core-2019-012 Project: Drupal core [1] Version: 8.8.x-dev8.7.x-dev7.x-dev Date: 2019-December-18 Security risk: *Critical* 17∕25 AC:Basic/A:User/CI:All/II:All/E:Proof/TD:Uncommon [2] Vulnerability: Multiple vulnerabilities Description: The Drupal project uses the third-party library Archive_Tar [3], which has released a security update that impacts some Drupal configurations. Multiple vulnerabilities are possible if Drupal is configured to allow .tar, .tar.gz, .bz2 or .tlz file uploads and processes them. The latest versions of Drupal update Archive_Tar to 1.4.9 to mitigate the file processing vulnerabilities. Solution: Install the latest version: * If you are using Drupal 7.x, upgrade to Drupal 7.69 [4]. * If you are using Drupal 8.7.x, upgrade to Drupal 8.7.11 [5]. * If you are using Drupal 8.8.x, upgrade to Drupal 8.8.1 [6]. Versions of Drupal 8 prior to 8.7.x are end-of-life and do not receive security coverage. Reported By: * Jasper Mattsson [7] Fixed By: * Lee Rowlands [8] of the Drupal Security Team * Peter Wolanin [9] of the Drupal Security Team * Sam Becker [10] * Jasper Mattsson [11] * David Rothstein [12] of the Drupal Security Team * michieltcs [13] * Ayesh Karunaratne [14] * Alex Pott [15] of the Drupal Security Team * Jess [16] of the Drupal Security Team * Samuel Mortenson [17] of the Drupal Security Team * Vijaya Chandran Mani [18] * Drew Webber [19] of the Drupal Security Team [1] https://www.drupal.org/project/drupal [2] https://www.drupal.org/security-team/risk-levels [3] https://pear.php.net/package/Archive_Tar/ [4] https://www.drupal.org/project/drupal/releases/7.69 [5] https://www.drupal.org/project/drupal/releases/8.7.11 [6] https://www.drupal.org/project/drupal/releases/8.8.1 [7] https://www.drupal.org/user/521118 [8] https://www.drupal.org/user/395439 [9] https://www.drupal.org/user/49851 [10] https://www.drupal.org/user/1485048 [11] https://www.drupal.org/user/521118 [12] https://www.drupal.org/user/124982 [13] https://www.drupal.org/user/3587972 [14] https://www.drupal.org/user/796148 [15] https://www.drupal.org/user/157725 [16] https://www.drupal.org/user/65776 [17] https://www.drupal.org/user/2582268 [18] https://www.drupal.org/user/93488 [19] https://www.drupal.org/user/255969

1 0

Drupal core - Moderately critical - Access bypass - SA-CORE-2019-011
by security-news＠drupal.org 18 Dec '19

18 Dec '19

View online: https://www.drupal.org/sa-core-2019-011 Project: Drupal core [1] Version: 8.8.x-dev8.7.x-dev Date: 2019-December-18 Security risk: *Moderately critical* 10∕25 AC:Basic/A:User/CI:Some/II:None/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Description: The Media Library module has a security vulnerability whereby it doesn't sufficiently restrict access to media items in certain configurations. Solution: * If you are using Drupal 8.7.x, you should upgrade to Drupal 8.7.11 [3]. * If you are using Drupal 8.8.x, you should upgrade to Drupal 8.8.1 [4]. Versions of Drupal 8 prior to 8.7.x are end-of-life and do not receive security coverage. Alternatively, you may mitigate this vulnerability by unchecking the "Enable advanced UI" checkbox on /admin/config/media/media-library. (This mitigation is not available in 8.7.x.) Reported By: * Adam G-H [5] Fixed By: * Adam G-H [6] * Jess [7] of the Drupal Security Team * Andrei Mateescu [8] * Greg Knaddison [9] of the Drupal Security Team * Alex Bronstein [10] of the Drupal Security Team * Sean Blommaert [11] * Lee Rowlands [12] of the Drupal Security Team [1] https://www.drupal.org/project/drupal [2] https://www.drupal.org/security-team/risk-levels [3] https://security.drupal.org/project/drupal/releases/8.7.11 [4] https://security.drupal.org/project/drupal/releases/8.8.1 [5] https://www.drupal.org/user/205645 [6] https://www.drupal.org/user/205645 [7] https://www.drupal.org/user/65776 [8] https://www.drupal.org/user/729614 [9] https://www.drupal.org/user/36762 [10] https://www.drupal.org/user/78040 [11] https://www.drupal.org/user/545912 [12] https://www.drupal.org/user/395439

1 0

Drupal core - Moderately critical - Denial of Service - SA-CORE-2019-009
by security-news＠drupal.org 18 Dec '19

18 Dec '19

View online: https://www.drupal.org/sa-core-2019-009 Project: Drupal core [1] Version: 8.8.x-dev8.7.x-dev Date: 2019-December-18 Security risk: *Moderately critical* 12∕25 AC:None/A:None/CI:None/II:None/E:Theoretical/TD:All [2] Vulnerability: Denial of Service Description: A visit to install.php can cause cached data to become corrupted. This could cause a site to be impaired until caches are rebuilt. Solution: Install the latest version: * If you are using Drupal 8.7.x, upgrade to Drupal 8.7.11 [3]. * If you are using Drupal 8.8.x, upgrade to Drupal 8.8.1 [4]. Versions of Drupal 8 prior to 8.7.x are end-of-life and do not receive security coverage. To mitigate this issue in any version of Drupal 8, you can also block access to install.php if it's not required. Reported By: * Drew Webber [5] of the Drupal Security Team Fixed By: * Drew Webber [6] of the Drupal Security Team * Lee Rowlands [7] of the Drupal Security Team * Heine [8] of the Drupal Security Team * Alex Pott [9] of the Drupal Security Team * Jess [10] of the Drupal Security Team * Damien McKenna [11] of the Drupal Security Team * David Snopek [12] of the Drupal Security Team * Nathaniel Catchpole [13] of the Drupal Security Team * Greg Knaddison [14] of the Drupal Security Team [1] https://www.drupal.org/project/drupal [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/drupal/releases/8.7.11 [4] https://www.drupal.org/project/drupal/releases/8.8.1 [5] https://www.drupal.org/user/255969 [6] https://www.drupal.org/user/255969 [7] https://www.drupal.org/user/395439 [8] https://www.drupal.org/user/17943 [9] https://www.drupal.org/user/157725 [10] https://www.drupal.org/user/65776 [11] https://www.drupal.org/user/108450 [12] https://www.drupal.org/user/266527 [13] https://www.drupal.org/user/35733 [14] https://www.drupal.org/user/36762

1 0

Modal Page - Moderately critical - Access bypass - SA-CONTRIB-2019-094
by security-news＠drupal.org 11 Dec '19

11 Dec '19

View online: https://www.drupal.org/sa-contrib-2019-094 Project: Modal Page [1] Version: 8.x-2.48.x-2.38.x-2.28.x-2.18.x-2.0 Date: 2019-December-11 Security risk: *Moderately critical* 10∕25 AC:Basic/A:User/CI:Some/II:None/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Description: This project enables administrators to create modal dialogs. The routes used by the module lacked proper permissions, allowing untrusted users to access, create and modify modal configurations. Solution: * If you use the Modal Page module 8.x-2.x, upgrade to 8.x-2.5 [3] * Review user permissions after updating to ensure only trusted users have access to manage modals. Reported By: * Will Mowlam [4] Fixed By: * Renato Gonçalves H [5] * Thalles Ferreira [6] Coordinated By: * Damien McKenna [7] of the Drupal Security Team [1] https://www.drupal.org/project/modal_page [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/modal_page/releases/8.x-2.5 [4] https://www.drupal.org/user/232558 [5] https://www.drupal.org/user/3326031 [6] https://www.drupal.org/user/3589086 [7] https://www.drupal.org/u/damienmckenna

1 0

Taxonomy access fix - Moderately critical - Access bypass - SA-CONTRIB-2019-093
by security-news＠drupal.org 11 Dec '19

11 Dec '19

View online: https://www.drupal.org/sa-contrib-2019-093 Project: Taxonomy access fix [1] Version: 8.x-2.68.x-2.58.x-2.4 Date: 2019-December-11 Security risk: *Moderately critical* 13∕25 AC:None/A:User/CI:Some/II:None/E:Theoretical/TD:All [2] Vulnerability: Access bypass Description: This module extends access handling of Drupal Core's Taxonomy module. The module doesn't sufficiently check, * if a given entity should be access controlled, defaulting to allowing access even to unpublished Taxonomy Terms. * if certain administrative routes should be access controlled, defaulting to allowing access even to users without permission to access these administrative routes. The vulnerability is mitigated by the facts, that * the user interface to change the status of Taxonomy Terms has been released in Drupal Core 8.8 and a custom or contributed module is required in earlier versions of Drupal Core to mark Taxonomy Terms as unpublished. * all entity operations (except the view operation) available on affected administrative routes still require appropriate permissions. * an attacker must have a role with permission to either access content or view a Taxonomy Term in a vocabulary. Solution: Install the latest version: * If you use taxonomy_access_fix 8.x-2.4 or later, upgrade to Taxonomy Access Fix 8.x-2.7 [3] Also see the Taxonomy Access Fix project page [4]. Reported By: * guedressel [5] Fixed By: * Julian Pustkuchen [6] * Patrick Fey [7] * Oleh Vehera [8] * guedressel [9] Coordinated By: * Greg Knaddison [10] of the Drupal Security Team * Damien McKenna [11] of the Drupal Security Team [1] https://www.drupal.org/project/taxonomy_access_fix [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/taxonomy_access_fix/releases/8.x-2.7 [4] https://www.drupal.org/project/taxonomy_access_fix [5] https://www.drupal.org/user/266710 [6] https://www.drupal.org/user/291091 [7] https://www.drupal.org/user/998680 [8] https://www.drupal.org/user/3260314 [9] https://www.drupal.org/user/266710 [10] https://www.drupal.org/u/greggles [11] https://www.drupal.org/u/damienmckenna

1 0

Smart Trim - Moderately critical - Cross site scripting - SA-CONTRIB-2019-092
by security-news＠drupal.org 11 Dec '19

11 Dec '19

View online: https://www.drupal.org/sa-contrib-2019-092 Project: Smart Trim [1] Version: 8.x-1.18.x-1.08.x-1.0-beta1 Date: 2019-December-11 Security risk: *Moderately critical* 13∕25 AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2] Vulnerability: Cross site scripting Description: The Smart Trim module allows site builders additional control with text summary fields. The module doesn't sufficiently filter text when certain options are selected. This vulnerability is mitigated by the fact that an attacker must have a role with the ability to create content on the site when certain options are selected for the trimmed output. Solution: Install the latest version: * If you use the Smart Trim module for Drupal 8.x, upgrade to smart_trim-8.x-1.2 [3] Also see the Smart Trim [4] project page. Reported By: * Anne [5] * Adam Shepherd [6] Fixed By: * Anne [7] * Mark Casias [8] Coordinated By: * Damien McKenna [9] of the Drupal Security Team [1] https://www.drupal.org/project/smart_trim [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/smart_trim/releases/8.x-1.2 [4] https://www.drupal.org/project/smart_trim [5] https://www.drupal.org/u/ckaotik [6] https://www.drupal.org/user/2650563 [7] https://www.drupal.org/u/ckaotik [8] https://www.drupal.org/user/206687 [9] https://www.drupal.org/u/damienmckenna

1 0

Permissions by Term - Moderately critical - Access bypass - SA-CONTRIB-2019-095
by security-news＠drupal.org 11 Dec '19

11 Dec '19

View online: https://www.drupal.org/sa-contrib-2019-095 Project: Permissions by Term [1] Date: 2019-December-11 Security risk: *Moderately critical* 13∕25 AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:Uncommon [2] Vulnerability: Access bypass Description: The Permissions by Term module extends Drupal by functionality for restricting access to single nodes via taxonomy terms. The module doesn't sufficiently restrict access to node previews, when the Search API module is used to display nodes in search result lists. Solution: Install the latest version: * If you use the Permissions by Term module for Drupal 8.x, upgrade to Version 8.x-2.0 [3] * The settings have been refactored. They are now bundled in the "permissions_by_term.settings.yml" file. There are not so many settings, so you can simply visit PbT's settings page and set the settings manually. Like the setting for "single term restriction". Also see the Permissions by Term [4] project page. Reported By: * Tamás Nagy [5] Fixed By: * Peter Majmesku [6] Coordinated By: * Greg Knaddison [7] of the Drupal Security Team [1] https://www.drupal.org/project/permissions_by_term [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/permissions_by_term/releases/8.x-2.0 [4] https://www.drupal.org/project/permissions_by_term [5] https://www.drupal.org/user/2252152 [6] https://www.drupal.org/user/786132 [7] https://www.drupal.org/u/greggles

1 0

Webform - Critical - Multiple vulnerabilities - SA-CONTRIB-2019-096
by security-news＠drupal.org 11 Dec '19

11 Dec '19

View online: https://www.drupal.org/sa-contrib-2019-096 Project: Webform [1] Version: 7.x-4.207.x-4.20-rc17.x-4.197.x-4.19-rc17.x-4.187.x-4.18-rc17.x-4.177.x-4.17-rc17.x-4.167.x-4.16-rc17.x-4.157.x-4.15-rc17.x-4.147.x-4.137.x-4.127.x-4.117.x-4.107.x-4.97.x-4.87.x-4.77.x-4.67.x-4.57.x-4.47.x-4.37.x-4.27.x-4.17.x-4.07.x-4.0-rc67.x-4.0-rc57.x-4.0-rc47.x-4.0-rc37.x-4.0-rc27.x-4.0-rc17.x-4.0-beta37.x-4.0-beta27.x-4.0-beta17.x-4.0-alpha107.x-4.0-alpha97.x-4.0-alpha87.x-4.0-alpha77.x-4.0-alpha67.x-4.0-alpha57.x-4.0-alpha47.x-4.0-alpha37.x-4.0-alpha27.x-4.0-alpha17.x-3.28-rc17.x-3.277.x-3.27-rc17.x-3.267.x-3.26-rc17.x-3.257.x-3.247.x-3.237.x-3.227.x-3.217.x-3.207.x-3.197.x-3.187.x-3.177.x-3.167.x-3.157.x-3.137.x-3.127.x-3.117.x-3.107.x-3.97.x-3.87.x-3.77.x-3.67.x-3.4-beta17.x-3.3-beta17.x-3.0-beta87.x-3.0-beta77.x-3.0-beta67.x-3.0-beta57.x-3.0-beta47.x-3.0-beta37.x-3.0-beta2 Date: 2019-December-11 Security risk: *Critical* 15∕25 AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:Default [2] Vulnerability: Multiple vulnerabilities Description: This module enables you to create forms to collect information from users and report, analyze and distribute it by email. The 7.x-3.x module doesn't sufficiently sanitize token values taken from query strings. If a query string token is used as the value of a markup component, an attacker can inject JavaScript into a page. The 7.x-4.x module doesn't sufficiently protect against an attacker changing the submission identifier of a draft webform, thereby overwriting another user's submission. Confidential information is not disclosed, but information can be overwritten and therefore lost or forged. The 7.x-4.x vulnerability is mitigated by the fact that an attacker must have a role with permission to submit a webform and the webform must have the advanced form setting of either 'Show "Save draft" button' and/or "Automatically save as draft between pages and when there are validation errors". Neither of these two options are enabled by default. Anonymous users cannot submit drafts and therefore cannot exploit this vulnerability. Solution: Install the latest version: * If you use the Webform 3.x module for Drupal 7.x, upgrade to Webform 7.x-3.29 [3] or to Webform 7.x-4.21. * If you use the Webform 4.x module for Drupal 7.x, upgrade to Webform 7.x-4.21 [4] Reported By: * Robin De Herdt [5] * Ayesh Karunaratne [6] Fixed By: * Robin De Herdt [7] * Ayesh Karunaratne [8] * Liam Morland [9] * Dan Chadwick [10] * Roman Zimmermann [11] Coordinated By: * Greg Knaddison [12] of the Drupal Security Team * Michael Hess [13] of the Drupal Security Team [1] https://www.drupal.org/project/webform [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/webform/releases/7.x-3.29 [4] https://www.drupal.org/project/webform/releases/7.x-4.21 [5] https://www.drupal.org/user/3555113 [6] https://www.drupal.org/user/796148 [7] https://www.drupal.org/user/3555113 [8] https://www.drupal.org/user/796148 [9] https://www.drupal.org/user/493050 [10] https://www.drupal.org/user/504278 [11] https://www.drupal.org/user/865256 [12] https://www.drupal.org/u/greggles [13] https://www.drupal.org/u/mlhess

1 0