September 2022 - Security-news

S3 File System - Moderately critical - Access bypass - SA-CONTRIB-2022-057
by security-news＠drupal.org 28 Sep '22

28 Sep '22

View online: https://www.drupal.org/sa-contrib-2022-057 Project: S3 File System [1] Date: 2022-September-28 Security risk: *Moderately critical* 10∕25 AC:Complex/A:None/CI:Some/II:None/E:Theoretical/TD:Uncommon [2] Vulnerability: Access bypass Description: This module enables you to utilize S3-compatible storage as a Drupal filesystem. The module doesn't sufficiently prevent file access across multiple filesystem schemes stored in the same bucket. This vulnerability is mitigated by the fact that an attacker must obtain a method to access arbitrary file paths, the site must have public or private takeover enabled, and the file metadata cache must be ignored. Solution: Install the latest version: * If you use the S3 File System module for Drupal 7.x, upgrade to S3 File System 7.x-2.14 [3] Reported By: * Conrad Lara [4] * Guy Elsmore-Paddock [5] Fixed By: * Conrad Lara [6] * Ron Shimshock [7] Coordinated By: * Greg Knaddison [8] of the Drupal Security Team [1] https://www.drupal.org/project/s3fs [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/s3fs/releases/7.x-2.14 [4] https://www.drupal.org/user/1790054 [5] https://www.drupal.org/user/156932 [6] https://www.drupal.org/user/1790054 [7] https://www.drupal.org/user/184990 [8] https://www.drupal.org/user/36762

1 0

Drupal core - Critical - Multiple vulnerabilities - SA-CORE-2022-016
by security-news＠drupal.org 28 Sep '22

28 Sep '22

View online: https://www.drupal.org/sa-core-2022-016 Project: Drupal core [1] Date: 2022-September-28 Security risk: *Critical* 18∕25 AC:Basic/A:Admin/CI:All/II:All/E:Proof/TD:All [2] Vulnerability: Multiple vulnerabilities Affected versions: >= 8.0.0 <9.3.22 || >= 9.4.0 <9.4.7 Description: Drupal uses the Twig [3] third-party library for content templating and sanitization. Twig has released a security update [4] that affects Drupal. Twig has rated the vulnerability as high severity. Drupal core's code extending Twig has also been updated to mitigate a related vulnerability. Multiple vulnerabilities are possible if an untrusted user has access to write Twig code, including potential unauthorized read access to private files, the contents of other files on the server, or database credentials. The vulnerability is mitigated by the fact that an exploit is only possible in Drupal core with a restricted access administrative permission. Additional exploit paths for the same vulnerability may exist with contributed or custom code that allows users to write Twig templates. Solution: Install the latest version: * If you are using Drupal 9.4, update to Drupal 9.4.7 [5]. * If you are using Drupal 9.3, update to Drupal 9.3.22 [6]. All versions of Drupal 9 prior to 9.3.x are end-of-life and do not receive security coverage. Note that Drupal 8 has reached its end of life [7]. Drupal 7 core does not include Twig and therefore is not affected. Reported By: * Fabien Potencier [8] * Nicolas Grekas [9] * James Williams [10] Fixed By: * xjm [11] of the Drupal Security Team * Alex Pott [12] of the Drupal Security Team * Sascha Grossenbacher [13] * Lee Rowlands [14] of the Drupal Security Team * Lauri Eskola [15], provisional member of the Drupal Security Team * Nathaniel Catchpole [16] of the Drupal Security Team * Dave Long [17], provisional member of the Drupal Security Team * cilefen [18] of the Drupal Security Team * James Williams [19] * Benji Fisher [20], provisional member of the Drupal Security Team [1] https://www.drupal.org/project/drupal [2] https://www.drupal.org/security-team/risk-levels [3] https://twig.symfony.com/ [4] https://symfony.com/blog/twig-security-release-possibility-to-load-a-templa… [5] https://www.drupal.org/project/drupal/releases/9.4.7 [6] https://www.drupal.org/project/drupal/releases/9.3.22 [7] https://www.drupal.org/psa-2021-06-29 [8] https://www.drupal.org/user/1467782 [9] https://www.drupal.org/user/3407972 [10] https://www.drupal.org/user/592268 [11] https://www.drupal.org/user/65776 [12] https://www.drupal.org/user/157725 [13] https://www.drupal.org/user/214652 [14] https://www.drupal.org/user/395439 [15] https://www.drupal.org/user/1078742 [16] https://www.drupal.org/user/35733 [17] https://www.drupal.org/user/246492 [18] https://www.drupal.org/user/1850070 [19] https://www.drupal.org/user/592268 [20] https://www.drupal.org/user/683300

1 0

Permissions by Term - Moderately critical - Access bypass - SA-CONTRIB-2022-056
by security-news＠drupal.org 07 Sep '22

07 Sep '22

View online: https://www.drupal.org/sa-contrib-2022-056 Project: Permissions by Term [1] Version: 3.1.18 Date: 2022-September-07 Security risk: *Moderately critical* 14∕25 AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Description: This module enables you to set content permissions based on taxonomy terms. The module doesn't sufficiently restrict access to translated and unpublished nodes. This vulnerability is mitigated by the fact that it only affects sites with translated content. Solution: Install the latest version: * If you use the Permissions by Term module for Drupal 9.x, upgrade to version 3.1.19 [3] Reported By: * federico prato [4] Fixed By: * federico prato [5] * Peter Majmesku [6] * Jess [7] of the Drupal Security Team Coordinated By: * Damien McKenna [8] of the Drupal Security Team * Greg Knaddison [9] 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/3.1.19 [4] https://www.drupal.org/user/1631800 [5] https://www.drupal.org/user/1631800 [6] https://www.drupal.org/user/786132 [7] https://www.drupal.org/user/65776 [8] https://www.drupal.org/user/108450 [9] https://www.drupal.org/user/36762

1 0

Permissions by Term - Moderately critical - Access bypass - SA-CONTRIB-2022-055
by security-news＠drupal.org 07 Sep '22

07 Sep '22

View online: https://www.drupal.org/sa-contrib-2022-055 Project: Permissions by Term [1] Version: 3.1.173.1.163.1.153.1.143.1.133.1.123.1.113.1.103.1.93.1.83.1.73.1.63.1.53.1.43.1.33.1.23.1.13.1.03.0.13.0.0 Date: 2022-September-07 Security risk: *Moderately critical* 14∕25 AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Description: This module enables you to restrict content via taxonomy terms and related permissions. The module doesn't sufficiently restrict cached content in certain circumstances. This vulnerability is mitigated by the fact that it only occurs when multiple entity types are enabled in the module. Solution: Install the latest version: * If you use the Permissions by Term module for Drupal 9.x, upgrade to version 3.1.19 [3] Reported By: * ytsurk [4] * Andy Fowlston [5] * Joseph [6] * Julian Pustkuchen [7] * Aleksi Peebles [8] Fixed By: * Peter Majmesku [9] * ytsurk [10] * Joseph [11] * Julian Pustkuchen [12] * Aleksi Peebles [13] * Ambient.Impact [14] * Stephen Mustgrave [15] * Jay McGraw [16] Coordinated By: * Damien McKenna [17] of the Drupal Security Team * Greg Knaddison [18] 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/3.1.19 [4] https://www.drupal.org/user/1153644 [5] https://www.drupal.org/user/220112 [6] https://www.drupal.org/user/3426415 [7] https://www.drupal.org/user/291091 [8] https://www.drupal.org/user/191965 [9] https://www.drupal.org/user/786132 [10] https://www.drupal.org/user/1153644 [11] https://www.drupal.org/user/3426415 [12] https://www.drupal.org/user/291091 [13] https://www.drupal.org/user/191965 [14] https://www.drupal.org/user/1131532 [15] https://www.drupal.org/user/3252890 [16] https://www.drupal.org/user/1124326 [17] https://www.drupal.org/user/108450 [18] https://www.drupal.org/user/36762

1 0

Next.js - Moderately critical - Access bypass - SA-CONTRIB-2022-054
by security-news＠drupal.org 07 Sep '22

07 Sep '22

View online: https://www.drupal.org/sa-contrib-2022-054 Project: Next.js [1] Version: 1.2.01.1.01.0.0 Date: 2022-September-07 Security risk: *Moderately critical* 12∕25 AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Description: The Next.js module provides an inline preview for content. Authenticated requests are made to Drupal to fetch JSON:API content and render them in an iframe from the decoupled Next.js site. The current implementation doesn’t sufficiently check access for fetching data. All requests made to Drupal are authenticated using a single scope with elevated content access. Users without access to content could be exposed to unauthorized content. Solution: If you use the Next.js module for Drupal 9.x: 1) Upgrade to version v1.3.0 [3]. 2) Edit the Next.js user and assign all roles that can be used as scopes. The granted roles will be filtered based on roles assigned to the current user. See the upgrade guide at https://next-drupal.org/docs/upgrade-guide [4]. Reported By: * Lauri Eskola [5] Fixed By: * Lauri Eskola [6] * shadcn [7] * Minnur Yunusov [8] Coordinated By: * Damien McKenna [9] of the Drupal Security Team [1] https://www.drupal.org/project/next [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/next/releases/1.3.0 [4] https://next-drupal.org/docs/upgrade-guide [5] https://www.drupal.org/user/1078742 [6] https://www.drupal.org/user/1078742 [7] https://www.drupal.org/user/571032 [8] https://www.drupal.org/user/702026 [9] https://www.drupal.org/user/108450

1 0