Security-news

security-news@drupal.org

1 participants
1782 discussions

Password Policy - Less critical - Denial of Service - SA-CONTRIB-2018-077
by security-news＠drupal.org 05 Dec '18

05 Dec '18

View online: https://www.drupal.org/sa-contrib-2018-077 Project: Password Policy [1] Version: 7.x-1.x-dev Date: 2018-December-05 Security risk: *Less critical* 9∕25 AC:Basic/A:None/CI:None/II:None/E:Theoretical/TD:Default [2] Vulnerability: Denial of Service Description: The Password Policy module makes it possible to set constraints on user passwords which disallow certain passwords. The "digit placement" constraint is vulnerable to Denial of Service attacks if an attacker submits specially crafted passwords which can cause a site to become unresponsive. This vulnerability is mitigated by the fact that a site must have the "digit placement" constraint enabled. Solution: Install the latest version: * If you use the Password Policy module for Drupal 7.x, upgrade to Password Policy 7.x-1.16 [3] Reported By: * Michael Sherron [4] Fixed By: * AohRveTPV [5] Coordinated By: * Greg Knaddison [6] of the Drupal Security Team * David Snopek [7] of the Drupal Security Team [1] https://www.drupal.org/project/password_policy [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/password_policy/releases/7.x-1.16 [4] https://www.drupal.org/user/470070 [5] https://www.drupal.org/user/2760115 [6] https://www.drupal.org/u/greggles [7] https://www.drupal.org/u/dsnopek

1 0

Date Reminder - Moderately critical - Access bypass - SA-CONTRIB-2018-076
by security-news＠drupal.org 28 Nov '18

28 Nov '18

View online: https://www.drupal.org/sa-contrib-2018-076 Project: Date Reminder [1] Date: 2018-November-28 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 allows registered users to request email reminders to be sent at a specified time before an event. The module doesn't sufficiently check access to nodes, allowing a user to set a reminder on a node that the user shouldn't be able to access. This can be mitigated with configuring DateReminder with Reminder Display: "Fieldset within a node" disables the potential exploit. Solution: Install the latest version: * If you use the Date Reminder module for Drupal 7.x, upgrade to Date Reminder 7.x-1.15 [3] Also see the Date Reminder [4] project page. Reported By: * than_nak87 [5] Fixed By: * dwillcox [6] * Balazs Janos Tatar [7] Provisional Security Team member Coordinated By: * Balazs Janos Tatar [8] Provisional Security Team member [1] https://www.drupal.org/project/datereminder [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/datereminder/releases/7.x-1.15 [4] https://www.drupal.org/project/datereminder [5] https://www.drupal.org/u/than_nak87 [6] https://www.drupal.org/user/230168 [7] https://www.drupal.org/user/649590 [8] https://www.drupal.org/user/649590

1 0

GatherContent - Moderately critical - Access bypass - SA-CONTRIB-2018-075
by security-news＠drupal.org 28 Nov '18

28 Nov '18

View online: https://www.drupal.org/sa-contrib-2018-075 Project: GatherContent [1] Date: 2018-November-28 Security risk: *Moderately critical* 13∕25 AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:All [2] Vulnerability: Access bypass Description: This module enables you to import and export data from the GatherContent service. The module didn't properly protect its administrative paths. Solution: * gathercontent 7.x versions prior to 7.x-3.5. Drupal core is not affected. If you do not use the contributed GatherContent [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the gathercontent module for Drupal 7.x, upgrade to gathercontent 7.x-3.5 [4] Reported By: * Francisco Rodriguez [5] Fixed By: * Roland Kovacsics [6] Coordinated By: * Michael Hess [7] of the Drupal Security Team * Greg Knaddison [8] of the Drupal Security Team [1] https://www.drupal.org/project/gathercontent [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/gathercontent [4] https://www.drupal.org/project/gathercontent/releases/7.x-3.5 [5] https://www.drupal.org/user/2744561 [6] https://www.drupal.org/user/3528385 [7] https://www.drupal.org/u/mlhess [8] https://www.drupal.org/u/greggles

1 0

Bootstrap - Moderately critical - Cross site scripting - SA-CONTRIB-2018-074
by security-news＠drupal.org 28 Nov '18

28 Nov '18

View online: https://www.drupal.org/sa-contrib-2018-074 Project: Bootstrap [1] Version: 7.x-3.228.x-3.14 Date: 2018-November-28 Security risk: *Moderately critical* 11∕25 AC:Complex/A:User/CI:Some/II:Some/E:Theoretical/TD:Uncommon [2] Vulnerability: Cross site scripting Description: This base theme bridges the gap between Drupal and the Bootstrap Framework. The theme doesn't sufficiently filter valid targets under the scenario of opening modals, popovers, and tooltips. This vulnerability is mitigated by the fact that an attacker must already have the ability to either: 1) Edit/save custom content that supplies a value for the data-target attribute by injecting malicious code. 2) Inject custom markup onto the page that further exploits the data-target attribute by injecting malicious code. This method of attack is highly unlikely if they already have this level of access. Note: while the base-theme does not provide either of these opportunities to do this out-of-the-box; a custom sub-theme may, however, be susceptible if it didn't sanitize or filter user provided input for XSS properly. Solution: Install the latest version *and* take additional manual steps (see below). * If you use the Drupal Bootstrap base-theme for Drupal 7.x, upgrade to 7.x-3.22 [3] * If you use the Drupal Bootstrap base-theme for Drupal 8.x, upgrade to 8.x-3.14 [4] *Extra Note:* The vulnerability fixed in the Bootstrap theme releases on Drupal.org is a by-product from forking parts of the external framework's JavaScript code. The external framework's vulnerability was first reported in a public issue [5] and later a fix for this vulnerability was merged [6] into the external framework, however an official release of the external framework has yet to be made. Users of this theme should take two additional steps: 1) Follow this external framework issue [7] for further information and to keep up-to-date on when you need to upgrade your sub-theme's external framework source. You may consider using the distributed files from the temporary branch master-xmr-v3-fixes [8] until an official release is made. 2) Review any custom code on your site that might have copied from the external framework's vulnerable code. Also see the Bootstrap [9] project page. Reported By: * Gomez_in_the_South [10] Fixed By: * Mark Carver [11] Coordinated By: * Greg Knaddison [12] of the Drupal Security Team * Samuel Mortenson of the Drupal Security Team [1] https://www.drupal.org/project/bootstrap [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/bootstrap/releases/7.x-3.22 [4] https://www.drupal.org/project/bootstrap/releases/8.x-3.14 [5] https://github.com/twbs/bootstrap/issues/20184 [6] https://github.com/twbs/bootstrap/issues/20184#ref-pullrequest-253002925 [7] https://github.com/twbs/bootstrap/issues/25679 [8] https://github.com/twbs/bootstrap/tree/master-xmr-v3-fixes [9] https://www.drupal.org/project/bootstrap [10] https://www.drupal.org/user/153735 [11] https://www.drupal.org/user/501638 [12] https://www.drupal.org/u/greggles

1 0

Paragraphs - Moderately critical - Access Bypass - SA-CONTRIB-2018-073
by security-news＠drupal.org 31 Oct '18

31 Oct '18

View online: https://www.drupal.org/sa-contrib-2018-073 Project: Paragraphs [1] Version: 8.x-1.4 Date: 2018-October-31 Security risk: *Moderately critical* 10∕25 AC:Complex/A:None/CI:None/II:Some/E:Theoretical/TD:Uncommon [2] Vulnerability: Access Bypass Description: The Paragraphs module allows Drupal Site Builders to make content organization cleaner so that you can give more editing power to end-users. The module doesn't sufficiently check access to create new paragraph entities which can cause access bypass issues when used in combination with other contributed modules. Solution: Install the latest version: * If you use the Paragraphs module for Drupal 8.x, upgrade to Paragraphs 8.x-1.5 [3] Also see the Paragraphs [4] project page. Reported By: * Sam Becker [5] Fixed By: * Sam Becker [6] * Alex Pott [7] of the Drupal Security Team * Sascha Grossenbacher [8] * Alex Bronstein [9] of the Drupal Security Team * Mateu Aguiló Bosch [10] * Miro Dietiker [11] Coordinated By: * Greg Knaddison [12] of the Drupal Security Team [1] https://www.drupal.org/project/paragraphs [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/node/3010590 [4] https://www.drupal.org/project/paragraphs [5] https://www.drupal.org/user/1485048 [6] https://www.drupal.org/user/1485048 [7] https://www.drupal.org/user/157725 [8] https://www.drupal.org/user/214652 [9] https://www.drupal.org/user/78040 [10] https://www.drupal.org/user/550110 [11] https://www.drupal.org/user/227761 [12] https://www.drupal.org/u/greggles

1 0

Session Limit - Critical - Insecure Session Management - SA-CONTRIB-2018-072
by security-news＠drupal.org 31 Oct '18

31 Oct '18

View online: https://www.drupal.org/sa-contrib-2018-072 Project: Session Limit [1] Version: 7.x-2.28.x-1.0-beta2 Date: 2018-October-31 Security risk: *Critical* 15∕25 AC:Complex/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] Vulnerability: Insecure Session Management Description: The session limit module enables a site administrator to set a policy around the number of active sessions users of the site may have. This is typically set to one so that you can only be logged in once with the same user account. In one configuration of the module, when a user logs in with another session elsewhere already active, the module asks the user which session should be closed before they can proceed with login. The module does not sufficiently tokenise the list of sessions so that the user's session keys can be found through inspection of the form. This vulnerability is mitigated by the fact that an attacker must already be able to intercept the contents of the HTML page to exploit the issue. That ability to intercept may come from Cross Site Scripting. This makes a Cross Site Scripting vulnerability worse than it would normally be. Solution: Install the latest version: * If you use the Session Limit module for Drupal 7.x, upgrade to 7.x-2.3 [3] * If you use the Session Limit module for Drupal 8.x, upgrade to 8.x-1.0-beta3 [4] Also see the Session Limit [5] project page. Reported By: * Simon Kapadia [6] Fixed By: * John Ennew [7] Coordinated By: * Greg Knaddison [8] of the Drupal Security Team [1] https://www.drupal.org/project/session_limit [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/session_limit/releases/7.x-2.3 [4] https://www.drupal.org/project/session_limit/releases/8.x-1.0-beta3 [5] https://www.drupal.org/project/session_limit [6] https://www.drupal.org/user/3524044 [7] https://www.drupal.org/user/1150042 [8] https://www.drupal.org/u/greggles

1 0

Decoupled Router - Critical - Access bypass - SA-CONTRIB-2018- 071
by security-news＠drupal.org 31 Oct '18

31 Oct '18

View online: https://www.drupal.org/sa-contrib-2018-071 Project: Decoupled Router [1] Version: 8.x-1.18.x-1.0 Date: 2018-October-31 Security risk: *Critical* 15∕25 AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:All [2] Vulnerability: Access bypass Description: This module enables you to resolve the provided Drupal path in order to find the canonical path and information about the resolved entity. This information includes entity type ID, entity ID, entity UUID and entity label. The module doesn't sufficiently check access before displaying entity labels. This leads to the display of labels on entities that are not be accessible, for example; titles of unpublished content. Solution: Install the latest version: * If you use the Decoupled Router module for Drupal 8.x, upgrade to Decoupled Router 8.x-1.2 [3] Also see the Decoupled Router [4] project page. Reported By: * Rainer Friederich [5] Fixed By: * Mateu Aguiló Bosch [6] Coordinated By: * Greg Knaddison (greggles) [7] of the Drupal Security Team * Michael Hess (mlhess) [8] of the Drupal Security Team [1] https://www.drupal.org/project/decoupled_router [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/decoupled_router/releases/8.x-1.2 [4] https://www.drupal.org/project/decoupled_router [5] https://www.drupal.org/user/3066367 [6] https://www.drupal.org/user/550110 [7] https://www.drupal.org/user/36762 [8] https://www.drupal.org/user/102818

1 0

Search Autocomplete - Moderately critical - Cross Site Scripting - SA-CONTRIB-2018-070
by security-news＠drupal.org 17 Oct '18

17 Oct '18

View online: https://www.drupal.org/sa-contrib-2018-070 Project: Search Autocomplete [1] Date: 2018-October-17 Security risk: *Moderately critical* 13∕25 AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2] Vulnerability: Cross Site Scripting CVE IDs: CVE-2018-7603 Description: This Search Autocomplete module enables you to autocomplete textfield using data from your website (nodes, comments, etc..). The module doesn't sufficiently filter user-entered text among the autocompletion items leading to a Cross Site Scripting (XSS) vulnerability. This vulnerability can be exploited by any user allowed to create one of the autocompletion item, for instance, nodes, users, comments. Solution: Install the latest version: * If you use the Search Autocomplete module for Drupal 7.x, upgrade to Search Autocomplete 7.x-4.8 [3] Also see the Search Autocomplete [4] project page. Reported By: * Simon Kapadia [5] Fixed By: * Dominique CLAUSE [6] Coordinated By: * Greg Knaddison [7] of the Drupal Security Team [1] https://www.drupal.org/project/search_autocomplete [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/search_autocomplete/releases/7.x-4.8 [4] https://www.drupal.org/project/search_autocomplete [5] https://www.drupal.org/user/3524044 [6] https://www.drupal.org/user/801982 [7] https://www.drupal.org/u/greggles

1 0

Workbench Moderation - Moderately critical - Access bypass - SA-CONTRIB-2018-067
by security-news＠drupal.org 17 Oct '18

17 Oct '18

View online: https://www.drupal.org/sa-contrib-2018-067 Project: Workbench Moderation [1] Date: 2018-October-17 Security risk: *Moderately critical* 11∕25 AC:Complex/A:User/CI:Some/II:Some/E:Theoretical/TD:Uncommon [2] Vulnerability: Access bypass Description: The Workbench Moderation module adds arbitrary moderation states to Drupal core's "unpublished" and "published" node states, and affects the behavior of node revisions when nodes are published. In some conditions, content moderation fails to check a users access to use certain transitions, leading to an access bypass. This issue is related to the Drupal Core release SA-CORE-2018-006 [3]. Solution: Install the latest version: * If you use the Workbench Moderation module for Drupal 8.x, upgrade to Workbench Moderation 8.x-1.4 [4] Also see the Drupal core [5] project page. Reported By: * Roland Kovacsics [6] Fixed By: * Wim Leers [7] * Daniel Wehner [8] * Sam Becker [9] * Tim Millwood [10] * Alex Pott [11] of the Drupal Security Team Coordinated By: * Greg Knaddison [12] of the Drupal Security Team * Lee Rowlands [13] of the Drupal Security Team [1] https://www.drupal.org/project/workbench_moderation [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/sa-core-2018-006 [4] https://www.drupal.org/project/workbench_moderation/releases/8.x-1.4 [5] https://www.drupal.org/project/drupal [6] https://www.drupal.org/user/3528385 [7] https://www.drupal.org/user/99777 [8] https://www.drupal.org/user/99340 [9] https://www.drupal.org/user/1485048 [10] https://www.drupal.org/user/227849 [11] https://www.drupal.org/user/157725 [12] https://www.drupal.org/u/greggles [13] https://www.drupal.org/u/larowlan

1 0

HTML Mail - Critical - Remote Code Execution - SA-CONTRIB-2018-069
by security-news＠drupal.org 17 Oct '18

17 Oct '18

View online: https://www.drupal.org/sa-contrib-2018-069 Project: HTML Mail [1] Date: 2018-October-17 Security risk: *Critical* 17∕25 AC:Basic/A:Admin/CI:All/II:All/E:Theoretical/TD:All [2] Vulnerability: Remote Code Execution Description: The HTML Mail module lets you theme your messages the same way you theme the rest of your website. When sending email some variables were not being sanitized for shell arguments, which could lead to remote code execution. This issue is related to the Drupal Core release SA-CORE-2018-006 [3]. Solution: Install the latest version: * If you are running Drupal 7.x, * update to 7.x-2.71 [4]. * In case you're still using 7.x-2.65, there is a version 7.x-2.66 [5] which has only the security patch applied, but you must realize that you are running old code and you're missing a number of bug fixes. Also see the HTML Mail [6] project page. Reported By: * Damien Tournoud [7] Fixed By: * Hans Salvisberg [8] Coordinated By: * Greg Knaddison [9] of the Drupal Security Team [1] https://www.drupal.org/project/htmlmail [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/sa-core-2018-006 [4] https://www.drupal.org/project/htmlmail/releases/7.x-2.71 [5] https://www.drupal.org/project/htmlmail/releases/7.x-2.66 [6] https://www.drupal.org/project/htmlmail [7] https://www.drupal.org/user/22211 [8] https://www.drupal.org/user/82964 [9] https://www.drupal.org/u/greggles

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Security-news