Security-news

security-news@drupal.org

1 participants
1782 discussions

Preview Link - Moderately critical - Access bypass - SA-CONTRIB-2019-004
by security-news＠drupal.org 23 Jan '19

23 Jan '19

View online: https://www.drupal.org/sa-contrib-2019-004 Project: Preview Link [1] Date: 2019-January-23 Security risk: *Moderately critical* 13∕25 AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:All [2] Vulnerability: Access bypass Description: The Preview Link module enables you to generate preview links so anonymous users can access unpublished revisions of content. The last release of the module introduced an access bypass allowing users to present invalid tokens but still access unpublished content. Solution: Install the latest version: * If you use the Preview Link module for Drupal 8.x, upgrade to Preview Link 8.x-1.1 [3] Also see the Preview Link [4] project page. Reported By: * Daniel [5] Fixed By: * Daniel [6] Coordinated By: * Lee Rowlands [7] of the Drupal Security Team [1] https://www.drupal.org/project/preview_link [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/preview_link/releases/8.x-1.1 [4] https://www.drupal.org/project/preview_link [5] https://www.drupal.org/user/81431 [6] https://www.drupal.org/user/81431 [7] https://www.drupal.org/user/larowlan

1 0

Drupal core - Critical - Arbitrary PHP code execution - SA-CORE-2019-002
by security-news＠drupal.org 16 Jan '19

16 Jan '19

View online: https://www.drupal.org/sa-core-2019-002 Project: Drupal core [1] Date: 2019-January-16 Security risk: *Critical* 16∕25 AC:Complex/A:Admin/CI:All/II:All/E:Theoretical/TD:All [2] Vulnerability: Arbitrary PHP code execution Description: A remote code execution vulnerability exists in PHP's built-in phar stream wrapper when performing file operations on an untrusted phar:// URI. Some Drupal code (core, contrib, and custom) may be performing file operations on insufficiently validated user input, thereby being exposed to this vulnerability. This vulnerability is mitigated by the fact that such code paths typically require access to an administrative permission or an atypical configuration. Solution: * If you are using Drupal 8.6.x, upgrade to Drupal 8.6.6 [3]. * If you are using Drupal 8.5.x or earlier, upgrade to Drupal 8.5.9 [4]. * If you are using Drupal 7.x, upgrade to Drupal 7.62 [5]. Versions of Drupal 8 prior to 8.5.x are end-of-life and do not receive security coverage. .. .phar added to dangerous extensions list The .phar file extension has been added to Drupal's dangerous extensions list, which means that any such file uploaded to a Drupal file field will automatically be converted to a text file (with the .txt extension) to prevent it from being executed. This is similar to how Drupal handles file uploads with a .php extension. .. phar:// stream wrapper disabled by default for Drupal 7 sites on PHP 5.3.2 and earlier The replacement stream wrapper is not compatible with PHP versions lower than 5.3.3. Drupal 8 requires a higher PHP version than that, but for Drupal 7 sites using lower PHP versions, the built-in phar stream wrapper has been disabled rather than replaced. Drupal 7 sites using PHP 5.2 (or PHP 5.3.0-5.3.2) that require phar support will need to re-enable the stream wrapper for it; however, note that re-enabling the stream wrapper will re-enable the insecure PHP behavior on those PHP versions. It is very uncommon to both be running a PHP version lower than 5.3.3 and to need phar support. If you're in that situation, consider upgrading your PHP version instead of restoring insecure phar support. Reported By: * Greg Knaddison [6] of the Drupal Security Team Fixed By: * Cash Williams [7] of the Drupal Security Team * Lee Rowlands [8] of the Drupal Security Team * Samuel Mortenson [9] of the Drupal Security Team * Jess [10] of the Drupal Security Team * Alex Pott [11] of the Drupal Security Team * Ted Bowman [12] * Michael Hess [13] of the Drupal Security Team * Alex Bronstein [14] of the Drupal Security Team * Fabian Franz [15] -------- ADDITIONAL INFORMATION ---------------------------------------------- Note: Going forward, Drupal core will issue individual security advisories for separate vulnerabilities included in the release, rather than lumping "multiple vulnerabilities" into a single advisory. All advisories released today: * SA-CORE-2019-001 [16] * SA-CORE-2019-002 [17] Updating to the latest Drupal core release will apply the fixes for all the above advisories. [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.6.6 [4] https://www.drupal.org/project/drupal/releases/8.5.9 [5] https://www.drupal.org/project/drupal/releases/7.62 [6] https://www.drupal.org/user/36762 [7] https://www.drupal.org/user/421070 [8] https://www.drupal.org/user/395439 [9] https://www.drupal.org/user/2582268 [10] https://www.drupal.org/user/65776 [11] https://www.drupal.org/user/157725 [12] https://www.drupal.org/user/240860 [13] https://www.drupal.org/user/102818 [14] https://www.drupal.org/user/78040 [15] https://www.drupal.org/user/693738 [16] https://www.drupal.org/sa-core-2019-001 [17] https://www.drupal.org/sa-core-2019-002

1 0

Drupal core - Critical - Third Party Libraries - SA-CORE-2019-001
by security-news＠drupal.org 16 Jan '19

16 Jan '19

View online: https://www.drupal.org/sa-core-2019-001 Project: Drupal core [1] Date: 2019-January-16 Security risk: *Critical* 16∕25 AC:Complex/A:User/CI:All/II:All/E:Proof/TD:Uncommon [2] Vulnerability: Third Party Libraries Description: Drupal core uses the third-party PEAR Archive_Tar library. This library has released a security update which impacts some Drupal configurations. Refer to CVE-2018-1000888 [3] for details. Solution: * If you are using Drupal 8.6.x, upgrade to Drupal 8.6.6 [4]. * If you are using Drupal 8.5.x or earlier, upgrade to Drupal 8.5.9 [5]. * If you are using Drupal 7.x, upgrade to Drupal 7.62 [6]. Versions of Drupal 8 prior to 8.5.x are end-of-life and do not receive security coverage. Reported By: * Ayesh Karunaratne [7] * farisv [8] Fixed By: * Jess [9] of the Drupal Security Team * Ayesh Karunaratne [10] * michieltcs [11] * Lee Rowlands [12] of the Drupal Security Team * Alex Pott [13] of the Drupal Security Team -------- ADDITIONAL INFORMATION ---------------------------------------------- Note: Going forward, Drupal core will issue individual security advisories for separate vulnerabilities included in the release, rather than lumping "multiple vulnerabilities" into a single advisory. All advisories released today: * SA-CORE-2019-001 [14] * SA-CORE-2019-002 [15] Updating to the latest Drupal core release will apply the fixes for all the above advisories. [1] https://www.drupal.org/project/drupal [2] https://www.drupal.org/security-team/risk-levels [3] https://nvd.nist.gov/vuln/detail/CVE-2018-1000888 [4] https://www.drupal.org/project/drupal/releases/8.6.6 [5] https://www.drupal.org/project/drupal/releases/8.5.9 [6] https://www.drupal.org/project/drupal/releases/7.62 [7] https://www.drupal.org/user/796148 [8] https://www.drupal.org/u/farisv [9] https://www.drupal.org/user/65776 [10] https://www.drupal.org/user/796148 [11] https://www.drupal.org/u/michieltcs [12] https://www.drupal.org/user/395439 [13] https://www.drupal.org/u/alexpott [14] https://www.drupal.org/sa-core-2019-001 [15] https://www.drupal.org/sa-core-2019-002

1 0

Provision - Moderately critical - Access bypass - SA-CONTRIB-2019-002
by security-news＠drupal.org 09 Jan '19

09 Jan '19

View online: https://www.drupal.org/sa-contrib-2019-002 Project: Provision [1] Version: 7.x-3.170 Date: 2019-January-09 Security risk: *Moderately critical* 12∕25 AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Description: Aegir is a Web hosting control panel program that provides a Drupal-based graphical interface designed to simplify deploying, managing and upgrading an entire network of Drupal, Wordpress and CiviCRM Web sites. The Provision module is a core piece of the Aegir platform. This module doesn't sufficiently shield multi-site installations or the PHP source code. This vulnerability is mitigated by the fact that the server must be using Apache. For multi-site installations, the server must host multiple sites on a common platform. Additionally an attacker must have a knowledge about used filenames and the server. Solution: Install the latest version: * If you use Aegir hosting system, upgrade to Provision 7.x-3.170 [3] Also see the Provision [4] project page. Reported By: * Cristian Segarra [5] Fixed By: * Cristian Segarra [6] * Jon Pugh [7] * anarcat [8] * Herman van Rink [9] * Colan Schwartz [10] Coordinated By: * Greg Knaddison [11] of the Drupal Security Team * Michael Hess [12] of the Drupal Security Team * Cash Williams [13] of the Drupal Security Team [1] https://www.drupal.org/project/provision [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/provision/releases/7.x-3.170 [4] https://www.drupal.org/project/provision [5] https://www.drupal.org/user/1501376 [6] https://www.drupal.org/user/1501376 [7] https://www.drupal.org/user/17028 [8] https://www.drupal.org/user/1274 [9] https://www.drupal.org/user/449000 [10] https://www.drupal.org/user/58704 [11] https://www.drupal.org/user/36762 [12] https://www.drupal.org/user/102818 [13] https://www.drupal.org/user/421070

1 0

Aegir HTTPS - Moderately critical - Access bypass - SA-CONTRIB-2019-003
by security-news＠drupal.org 09 Jan '19

09 Jan '19

View online: https://www.drupal.org/sa-contrib-2019-003 Project: Aegir HTTPS [1] Date: 2019-January-09 Security risk: *Moderately critical* 12∕25 AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Description: Aegir is a Web hosting control panel program that provides a Drupal-based graphical interface designed to simplify deploying, managing and upgrading an entire network of Drupal, Wordpress and CiviCRM Web sites. The Hosting HTTPS module is a commonly used piece of the Aegir platform. This module doesn't sufficiently shield multi-site installations. This vulnerability is mitigated by the fact that the server must be using Apache and must host multiple sites on a common platform. An attacker must have a knowledge about used filenames and the server. Solution: Install the latest version: * If you use Aegir hosting system, upgrade to Aegir HTTPS 7.x-3.170 [3] Also see the Aegir HTTPS [4] project page. Reported By: * Cristian Segarra [5] Fixed By: * Cristian Segarra [6] * Jon Pugh [7] * anarcat [8] * Herman van Rink [9] * Colan Schwartz [10] Coordinated By: * Greg Knaddison [11] of the Drupal Security Team * Michael Hess [12] of the Drupal Security Team * Cash Williams [13] of the Drupal Security Team [1] https://www.drupal.org/project/hosting_https [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/hosting_https/releases/7.x-3.170 [4] https://www.drupal.org/project/hosting_https [5] https://www.drupal.org/user/1501376 [6] https://www.drupal.org/user/1501376 [7] https://www.drupal.org/user/17028 [8] https://www.drupal.org/user/1274 [9] https://www.drupal.org/user/449000 [10] https://www.drupal.org/user/58704 [11] https://www.drupal.org/user/36762 [12] https://www.drupal.org/user/102818 [13] https://www.drupal.org/user/421070

1 0

Phone Field - Critical - SQL Injection - SA-CONTRIB-2019-001
by security-news＠drupal.org 09 Jan '19

09 Jan '19

View online: https://www.drupal.org/sa-contrib-2019-001 Project: Phone Field [1] Date: 2019-January-09 Security risk: *Critical* 16∕25 AC:Basic/A:User/CI:All/II:All/E:Theoretical/TD:Uncommon [2] Vulnerability: SQL Injection Description: This module provides a phone field for Drupal 7 that supports the HTML5 tel:-schema. In an API function that is not used by the module, the name for the phone field is not sufficiently sanitised when using it in database queries. This vulnerability is mitigated by the fact that it affects an unused function. A site is only vulnerable if it has custom code that uses the phonefield_get_entity_id() function and exposes control over the $field parameter to visitors to the site. Solution: Install the latest version: * If you use the phonefield module for Drupal 7.x, upgrade to phonefield 7.x-1.1 [3] Also see the Phone Field [4] project page. Reported By: * Drew Webber [5] Fixed By: * Drew Webber [6] * Gisle Hannemyr [7] Coordinated By: * Greg Knaddison [8] of the Drupal Security Team * Drew Webber [9] [1] https://www.drupal.org/project/phonefield [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/phonefield/releases/7.x-1.1 [4] https://www.drupal.org/project/phonefield [5] https://www.drupal.org/user/255969 [6] https://www.drupal.org/user/255969 [7] https://www.drupal.org/user/409554 [8] https://www.drupal.org/user/36762 [9] https://www.drupal.org/user/255969

1 0

JSON:API - Moderately critical - Access bypass - SA-CONTRIB-2018-081
by security-news＠drupal.org 19 Dec '18

19 Dec '18

View online: https://www.drupal.org/sa-contrib-2018-081 Project: JSON:API [1] Date: 2018-December-19 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 provides a JSON:API specification-compliant HTTP API for accessing and manipulating Drupal content and configuration entities. The module doesn't sufficiently check access when responding to certain filtered collection requests, thereby causing an access bypass vulnerability. In order to fix this issue, two new hooks were added: hook_jsonapi_ENTITY_TYPE_filter_access() and hook_jsonapi_entity_field_filter_access(). Sites with custom entity types and/or with entity or field access customizations may need to implement these newly introduced hooks. Solution: Install the latest version: * If you use the JSON:API module 8.x-1.x for Drupal 8.x, upgrade to JSON API 8.x-1.24 [3] Also see the JSON:API [4] project page. Reported By: * Gabe Sullice [5] * Lauri Eskola [6] Fixed By: * Gabe Sullice [7] * Wim Leers [8] * Alex Bronstein [9] of the Drupal Security Team * Tobias Zimmermann [10] * Andrei Mateescu [11] * Mateu Aguiló Bosch [12] * Hristo Chonov [13] * Daniel Wehner [14] * Sascha Grossenbacher [15] * Kristiaan Van den Eynde [16] * Lee Rowlands [17] of the Drupal Security Team Coordinated By: * Alex Bronstein [18] of the Drupal Security Team [1] https://www.drupal.org/project/jsonapi [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/node/3021532 [4] https://www.drupal.org/project/jsonapi [5] https://www.drupal.org/user/2287430 [6] https://www.drupal.org/user/1078742 [7] https://www.drupal.org/user/2287430 [8] https://www.drupal.org/user/99777 [9] https://www.drupal.org/user/78040 [10] https://www.drupal.org/user/107158 [11] https://www.drupal.org/user/729614 [12] https://www.drupal.org/user/550110 [13] https://www.drupal.org/user/2901211 [14] https://www.drupal.org/user/99340 [15] https://www.drupal.org/user/214652 [16] https://www.drupal.org/user/1345130 [17] https://www.drupal.org/user/395439 [18] https://www.drupal.org/user/78040

1 0

E-Sign - Moderately critical - Cross site scripting - SA-CONTRIB-2018-080
by security-news＠drupal.org 19 Dec '18

19 Dec '18

View online: https://www.drupal.org/sa-contrib-2018-080 Project: E-Sign [1] Version: 7.x-1.9 Date: 2018-December-19 Security risk: *Moderately critical* 14∕25 AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] Vulnerability: Cross site scripting Description: This module allows for integration of Signature Pad, an electronic-signing script, into Drupal for both nodes (content), the Field API (FAPI), and Webforms. The module doesn't sufficiently filter user input when displaying a signature. The vulnerability is mitigated by the fact that an attacker must have the ability to submit a signature. That permission might be associated with submitting a webform or creating or editing a node depending on site configuration. Solution: Install the latest version: * If you use the Esign module for Drupal 7.x, upgrade to Esign 7.x-1.10 [3] Also see the E-Sign [4] project page. Reported By: * Mitch Portier [5] Fixed By: * Adam Weiss [6] * Mitch Portier [7] Coordinated By: * Greg Knaddison [8] of the Drupal Security Team [1] https://www.drupal.org/project/esign [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/esign/releases/7.x-1.10 [4] https://www.drupal.org/project/esign [5] https://www.drupal.org/user/2284182 [6] https://www.drupal.org/user/1199320 [7] https://www.drupal.org/user/2284182 [8] https://www.drupal.org/u/greggles

1 0

Responsive Menus - Moderately critical - Cross site scripting - SA-CONTRIB-2018-079
by security-news＠drupal.org 05 Dec '18

05 Dec '18

View online: https://www.drupal.org/sa-contrib-2018-079 Project: Responsive Menus [1] Version: 7.x-1.x-dev Date: 2018-December-05 Security risk: *Moderately critical* 13∕25 AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2] Vulnerability: Cross site scripting Description: This module enables you to collapse your sites main menu on mobile, and show a menu toggle button. The module doesn't sufficiently sanitize configuration settings provided by users which leads 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 responsive menus". Solution: Install the latest version: * If you use the responsive_menus module for Drupal 7.x, upgrade to responsive_menus 7.x-1.7 [3] Reported By: * Ayesh Karunaratne [4] Fixed By: * Joshua Walker [5] Coordinated By: * Michael Hess [6] of the Drupal Security Team * David Snopek [7] of the Drupal Security Team [1] https://www.drupal.org/project/responsive_menus [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/responsive_menus/releases/7.x-1.7 [4] https://www.drupal.org/user/796148 [5] https://www.drupal.org/user/433663 [6] https://www.drupal.org/u/mlhess [7] https://www.drupal.org/u/dsnopek

1 0

Salesforce Suite - Moderately critical - Access bypass - SA-CONTRIB-2018-078
by security-news＠drupal.org 05 Dec '18

05 Dec '18

View online: https://www.drupal.org/sa-contrib-2018-078 Project: Salesforce Suite [1] Date: 2018-December-05 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 Drupal to synchronize entities with Salesforce records. The module includes a page that does not sufficiently protect access rights, resulting in potential information disclosure. This vulnerability is mitigated by the fact that only Drupal entity title and IDs, and Salesforce record IDs are exposed. Entity content and metadata are appropriately protected. Disclosure of Salesforce ID does not confer any additional privileges. Solution: Install the latest version: * If you use the Salesforce Suite module for Drupal 8.x, upgrade to Salesforce Suite 8.x-3.1 [3] Also see the Salesforce Suite [4] project page. Reported By: * Oskar Schöldström [5] Fixed By: * Aaron Bauman [6] * Gabriel Carleton-Barnes [7] Coordinated By: * Greg Knaddison [8] of the Drupal Security Team [1] https://www.drupal.org/project/salesforce [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/salesforce/releases/8.x-3.1 [4] https://www.drupal.org/project/salesforce [5] https://www.drupal.org/user/799618 [6] https://www.drupal.org/user/384578 [7] https://www.drupal.org/user/1682976 [8] 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