- Security-news - lists.drupal.org

Media Library Form API Element - Moderately critical - Information Disclosure - SA-CONTRIB-2023-004
by security-news＠drupal.org 18 Jan '23

18 Jan '23

View online: https://www.drupal.org/sa-contrib-2023-004 Project: Media Library Form API Element [1] Version: 8.x-1.38.x-1.28.x-1.1 Date: 2023-January-18 Security risk: *Moderately critical* 13∕25 AC:None/A:User/CI:Some/II:None/E:Theoretical/TD:All [2] Vulnerability: Information Disclosure Affected versions: >=2.0 <2.0.6 Description: This module enables you to use the media library in custom forms without the Media Library Widget. The module does not properly check entity access in some circumstances. This may result in users with access to edit content seeing metadata about media items they are not authorized to access. The vulnerability is mitigated by the fact that the inaccessible media will only be visible to users who can already edit content that includes a media reference field. Solution: Install the latest version: * If you use the Media Library Form API Element module versions 2.x for Drupal 9 or 10, upgrade to 2.0.6 [3]. * If you use the Media Library Form API Element module version 8.x-1.* they are all affected and are no longer supported. You should upgrade to 2.0.6 [4]. Reported By: * Benji Fisher [5] of the Drupal Security Team * Dan Flanagan [6] Fixed By: * Kim Kennof [7] * Lauri Eskola [8] * Alex Bronstein [9] of the Drupal Security Team * Luke Leber [10] * Lee Rowlands [11] of the Drupal Security Team Coordinated By: * xjm [12] of the Drupal Security Team * Lee Rowlands [13] of the Drupal Security Team * Benji Fisher [14] of the Drupal Security Team [1] https://www.drupal.org/project/media_library_form_element [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/media_library_form_element/releases/2.0.6 [4] https://www.drupal.org/project/media_library_form_element/releases/2.0.6 [5] https://www.drupal.org/user/683300 [6] https://www.drupal.org/user/3615359 [7] https://www.drupal.org/user/333515 [8] https://www.drupal.org/user/1078742 [9] https://www.drupal.org/user/78040 [10] https://www.drupal.org/user/3509746 [11] https://www.drupal.org/user/395439 [12] https://www.drupal.org/user/65776 [13] https://www.drupal.org/user/395439 [14] https://www.drupal.org/user/395439

1 0

Drupal core - Moderately critical - Information Disclosure - SA-CORE-2023-001
by security-news＠drupal.org 18 Jan '23

18 Jan '23

View online: https://www.drupal.org/sa-core-2023-001 Project: Drupal core [1] Date: 2023-January-18 Security risk: *Moderately critical* 12∕25 AC:None/A:User/CI:Some/II:None/E:Theoretical/TD:Default [2] Vulnerability: Information Disclosure Affected versions: >=8.0.0 <9.4.10 || >=9.5.0 <9.5.2 || >=10.0.0 <10.0.2 Description: The Media Library module does not properly check entity access in some circumstances. This may result in users with access to edit content seeing metadata about media items they are not authorized to access. The vulnerability is mitigated by the fact that the inaccessible media will only be visible to users who can already edit content that includes a media reference field. This advisory is not covered by Drupal Steward [3]. Solution: Install the latest version: * If you are using Drupal 10.0, update to Drupal 10.0.2 [4]. * If you are using Drupal 9.5, update to Drupal 9.5.2 [5]. * If you are using Drupal 9.4, update to Drupal 9.4.10 [6]. All versions of Drupal 9 prior to 9.4.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 the Media Library module and therefore is not affected. Reported By: * Dan Flanagan [8] Fixed By: * Lee Rowlands [9] of the Drupal Security Team * Dan Flanagan [10] * Sean Blommaert [11] * xjm [12] of the Drupal Security Team * Benji Fisher [13] of the Drupal Security Team * Dave Long [14] of the Drupal Security Team * Jen Lampton [15], provisional member of the Drupal Security Team * Sascha Grossenbacher [16] * Lauri Eskola [17], 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://www.drupal.org/steward [4] https://www.drupal.org/project/drupal/releases/10.0.2 [5] https://www.drupal.org/project/drupal/releases/9.5.2 [6] https://www.drupal.org/project/drupal/releases/9.4.10 [7] https://www.drupal.org/psa-2021-06-29 [8] https://www.drupal.org/user/3615359 [9] https://www.drupal.org/user/395439 [10] https://www.drupal.org/user/3615359 [11] https://www.drupal.org/user/545912 [12] https://www.drupal.org/user/65776 [13] https://www.drupal.org/user/683300 [14] https://www.drupal.org/user/246492 [15] https://www.drupal.org/user/85586 [16] https://www.drupal.org/user/214652 [17] https://www.drupal.org/user/1078742

1 0

Private Taxonomy Terms - Moderately critical - Access bypass - SA-CONTRIB-2023-001
by security-news＠drupal.org 11 Jan '23

11 Jan '23

View online: https://www.drupal.org/sa-contrib-2023-001 Project: Private Taxonomy Terms [1] Date: 2023-January-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 module enables users to create 'private' vocabularies. The module doesn't enforce permissions appropriately for the taxonomy overview page and overview form. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "Administer own taxonomy" or "View private taxonomies" Solution: Install the latest version: * If you use the Private Taxonomy Terms module for Drupal 8.x, upgrade to Private Taxonomy Terms 8.x-2.6 [3] Reported By: * Giuseppe [4] Fixed By: * Conrad Lara [5] * Giuseppe [6] Coordinated By: * Damien McKenna [7] of the Drupal Security Team * Jess [8] of the Drupal Security Team * Greg Knaddison [9] of the Drupal Security Team [1] https://www.drupal.org/project/private_taxonomy [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/private_taxonomy/releases/8.x-2.6 [4] https://www.drupal.org/user/3521392 [5] https://www.drupal.org/user/1790054 [6] https://www.drupal.org/user/3521392 [7] https://www.drupal.org/user/108450 [8] https://www.drupal.org/user/65776 [9] https://www.drupal.org/user/36762

1 0

File (Field) Paths - Moderately critical - Access bypass - SA-CONTRIB-2022-065
by security-news＠drupal.org 14 Dec '22

14 Dec '22

View online: https://www.drupal.org/sa-contrib-2022-065 Project: File (Field) Paths [1] Date: 2022-December-14 Security risk: *Moderately critical* 12∕25 AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Description: The File (Field) Paths module extends the default functionality of Drupal's core File module, by adding the ability to use entity-based tokens in destination paths and file names. The module's default configuration could temporarily expose private files to anonymous visitors. *Important note:* to fix the problem, database updates must be run in addition to updating the module. It's possible to make a configuration change to mitigate this problem in the admin UI at /admin/config/media/file-system/filefield-paths - the temp file location should use either the temporary:// or private:// stream wrapper if uploaded files should not be exposed publicly. This vulnerability is mitigated by the fact that an attacker must be able to guess the temporary path used for file upload. Solution: Install the latest version: * If you use the File (Field) Paths module for Drupal 7.x, upgrade to File (Field) Paths 7.x-1.2 [3] Reported By: * Hayato Goto [4] * Drew Webber [5] of the Drupal Security Team * Steve Bink [6] Fixed By: * Hayato Goto [7] * David Snopek [8] of the Drupal Security Team * Vijay Mani [9] provisional member of the Drupal Security Team * Drew Webber [10] of the Drupal Security Team * Oleh Vehera [11] * Damien McKenna [12] of the Drupal Security Team Coordinated By: * David Snopek [13] of the Drupal Security Team * Drew Webber [14] of the Drupal Security Team * Greg Knaddison [15] of the Drupal Security Team [1] https://www.drupal.org/project/filefield_paths [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/filefield_paths/releases/7.x-1.2 [4] https://www.drupal.org/user/2844385 [5] https://www.drupal.org/user/255969 [6] https://www.drupal.org/user/3427991 [7] https://www.drupal.org/user/2844385 [8] https://www.drupal.org/user/266527 [9] https://www.drupal.org/user/93488 [10] https://www.drupal.org/user/255969 [11] https://www.drupal.org/user/3260314 [12] https://www.drupal.org/user/108450 [13] https://www.drupal.org/u/dsnopek [14] https://www.drupal.org/u/mcdruid [15] https://www.drupal.org/user/36762

1 0

H5P - Create and Share Rich Content and Applications - Moderately critical - Remote Code Execution - SA-CONTRIB-2022-064
by security-news＠drupal.org 14 Dec '22

14 Dec '22

View online: https://www.drupal.org/sa-contrib-2022-064 Project: H5P - Create and Share Rich Content and Applications [1] Date: 2022-December-14 Security risk: *Moderately critical* 12∕25 AC:Complex/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2] Vulnerability: Remote Code Execution Description: This module enables you to create interactive content. The module doesn't sufficiently stop path traversal attacks through zipped filenames for the uploadable .h5p files. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "update h5p libraries". In addition, it is only exploitable on Windows servers. Solution: Install the latest version: * If you use the H5P module for Drupal 7.x, upgrade to H5P 7.x-1.51 [3] Reported By: Disclosed publicly. Fixed By: * Frode Petterson [4] * paalj [5] Coordinated By: * Greg Knaddison [6] of the Drupal Security Team [1] https://www.drupal.org/project/h5p [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/h5p/releases/7.x-1.51 [4] https://www.drupal.org/user/823190 [5] https://www.drupal.org/user/1091732 [6] https://www.drupal.org/user/36762

1 0

Entity Registration - Moderately critical - Access bypass - SA-CONTRIB-2022-063
by security-news＠drupal.org 07 Dec '22

07 Dec '22

View online: https://www.drupal.org/sa-contrib-2022-063 Project: Entity Registration [1] Date: 2022-December-07 Security risk: *Moderately critical* 13∕25 AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Affected versions: >=7.1.0 <7.1.9 Description: This module enables you to create registration entities related to nodes. The module doesn't sufficiently restrict update access to a user's own registrations. This vulnerability is mitigated by the fact that an attacker must have the "update own [registration type]" permission. Solution: Install the latest version: * If you use the Entity Registration module for Drupal 7.x, upgrade to Entity Registration 7.x-1.9 [3] release *Note:* Sites that allow non-administrative users to manage registrations because the users can update the registration host entity and have "update own registration" permission for a given registration type, may need to give those users the "administer own registration" permission for them to retain the ability to manage registrations after installing this upgrade. Reported By: * Joël Pittet [4] Fixed By: * Joël Pittet [5] * Maria Fisher [6] * john.oltman [7] Coordinated By: * James Gilliland [8] of the Drupal Security Team Reported at: 20 November 2022 [1] https://www.drupal.org/project/registration [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/registration/releases/7.x-1.9 [4] https://www.drupal.org/user/160302 [5] https://www.drupal.org/user/160302 [6] https://www.drupal.org/user/2210776 [7] https://www.drupal.org/user/699926 [8] https://www.drupal.org/user/48673

1 0

Open Social - Moderately critical - Access bypass - SA-CONTRIB-2022-062
by security-news＠drupal.org 30 Nov '22

30 Nov '22

View online: https://www.drupal.org/sa-contrib-2022-062 Project: Open Social [1] Date: 2022-November-30 Security risk: *Moderately critical* 10∕25 AC:Basic/A:User/CI:None/II:Some/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Affected versions: >=11.4.0 <11.4.9 || >=11.5.0 <11.5.1 Description: Social Private Message module allows users on the platform to allow users to send private messages to each other. The module does not properly perform the correct access checks for certain operations. Solution: Install the latest version: * If you use the Open Social distribution for Drupal 9.x, upgrade to Open Social 11.5.1 [3] * If you use the Open Social distribution for Drupal 9.x, upgrade to Open Social 11.4.9 [4] Reported By: * zanvidmar [5] Fixed By: * Navneet Singh [6] * zanvidmar [7] Coordinated By: * Damien McKenna [8] of the Drupal Security Team * Greg Knaddison [9] of the Drupal Security Team [1] https://www.drupal.org/project/social [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/social/releases/11.5.1 [4] https://www.drupal.org/project/social/releases/11.4.9 [5] https://www.drupal.org/user/3003243 [6] https://www.drupal.org/user/3200545 [7] https://www.drupal.org/user/3003243 [8] https://www.drupal.org/user/108450 [9] https://www.drupal.org/user/36762

1 0

Open Social - Moderately critical - Access bypass - SA-CONTRIB-2022-061
by security-news＠drupal.org 30 Nov '22

30 Nov '22

View online: https://www.drupal.org/sa-contrib-2022-061 Project: Open Social [1] Date: 2022-November-30 Security risk: *Moderately critical* 13∕25 AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:Uncommon [2] Vulnerability: Access bypass Affected versions: >=11.4.0 <11.4.9 || >=11.5.0 <11.5.1 Description: Social Flexible Group is an Open Social extension that allows users to create groups with many different configurations. In specific uncommon scenarios, where a platform doesn't have any flexible groups with the "Group members only (secret)" visibility, community groups are visible to anonymous users on the /all-groups page. No other group information is revealed since group access is not affected by this issue. This vulnerability is mitigated by creating a Flexible Group with visibility "Group members only (secret)". Solution: Install the latest version: * If you use the Open Social distribution for Drupal 9.x, upgrade to Open Social 11.5.1 [3] * If you use the Open Social distribution for Drupal 9.x, upgrade to Open Social 11.4.9 [4] Reported By: * Tiago Siqueira [5] Fixed By: * Tiago Siqueira [6] * Alexander Varwijk [7] * Navneet Singh [8] Coordinated By: * cilefen [9] of the Drupal Security Team * Damien McKenna [10] of the Drupal Security Team * Greg Knaddison [11] of the Drupal Security Team [1] https://www.drupal.org/project/social [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/social/releases/11.5.1 [4] https://www.drupal.org/project/social/releases/11.4.9 [5] https://www.drupal.org/user/2822445 [6] https://www.drupal.org/user/2822445 [7] https://www.drupal.org/user/1868952 [8] https://www.drupal.org/user/3200545 [9] https://www.drupal.org/user/1850070 [10] https://www.drupal.org/user/108450 [11] https://www.drupal.org/user/36762

1 0

Social Base - Moderately critical - Access bypass - SA-CONTRIB-2022-060
by security-news＠drupal.org 30 Nov '22

30 Nov '22

View online: https://www.drupal.org/sa-contrib-2022-060 Project: Social Base [1] Date: 2022-November-30 Security risk: *Moderately critical* 14∕25 AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Affected versions: >=2.3 <2.3.4 || >=2.4 <2.4.3 Description: The Social Base theme is designed as a base theme for Open Social. This base theme holds has a lot of sensible defaults. It doesn't however contain much styling. We expect developers to want to change this for their own project. When content within the Open Social distribution is placed within a group then the Socialbase theme renders a link to that group on the content view page. The link to groups was rendered without sufficiently checking that the viewing user has access to the group. When creating public content in a non-public group this could lead to exposing the existence of the group and the group title to unauthorized users. The group itself remained inaccessible. Solution: Install the latest version: * If you use the Socialbase module theme for Drupal 8.x/9.x, upgrade to Socialbase 2.4.3 [3] * If you use the Socialbase module theme for Drupal 8.x/9.x, upgrade to Socialbase 2.3.4 [4] Reported By: * Alexander Varwijk [5] Fixed By: * Alexander Varwijk [6] * Ronald te Brake [7] * Navneet Singh [8] Coordinated By: * Damien McKenna [9] of the Drupal Security Team * Greg Knaddison [10] of the Drupal Security Team [1] https://www.drupal.org/project/socialbase [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/socialbase/releases/2.4.3 [4] https://www.drupal.org/project/socialbase/releases/2.3.4 [5] https://www.drupal.org/user/1868952 [6] https://www.drupal.org/user/1868952 [7] https://www.drupal.org/user/2314038 [8] https://www.drupal.org/user/3200545 [9] https://www.drupal.org/user/108450 [10] https://www.drupal.org/user/36762

1 0

Search API - Moderately critical - Information Disclosure - SA-CONTRIB-2022-059
by security-news＠drupal.org 19 Oct '22

19 Oct '22

View online: https://www.drupal.org/sa-contrib-2022-059 Project: Search API [1] Date: 2022-October-19 Security risk: *Moderately critical* 13∕25 AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:Uncommon [2] Vulnerability: Information Disclosure Description: This module enables you to build searches using a wide range of features, data sources and backends. The module doesn't in all cases correctly detect whether a given search is active on the current page, leading to potential information disclosure for some setups. This vulnerability is mitigated by the fact that only very specific setups will have this problem and there is no way for an attacker to trigger it. Solution: Install the latest version: * If you use the Search API module for Drupal 9.x/10.x, upgrade to Search API 8.x-1.27 [3] Reported By: * Markus Kalkbrenner [4] Fixed By: * Gerhard Killesreiter [5] of the Drupal Security Team * Joris Vercammen [6] * Markus Kalkbrenner [7] * Thomas Seidl [8] * Damien McKenna [9] of the Drupal Security Team Coordinated By: * Michael Hess [10] of the Drupal Security Team [1] https://www.drupal.org/project/search_api [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/search_api/releases/8.x-1.27 [4] https://www.drupal.org/user/124705 [5] https://www.drupal.org/user/83 [6] https://www.drupal.org/user/2393360 [7] https://www.drupal.org/user/124705 [8] https://www.drupal.org/user/205582 [9] https://www.drupal.org/user/108450 [10] https://www.drupal.org/u/mlhess

1 0