Hírolvasó
S3 File System - Moderately critical - Access bypass - SA-CONTRIB-2022-057
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
- Greg Knaddison of the Drupal Security Team
Drupal core - Critical - Multiple vulnerabilities - SA-CORE-2022-016
Drupal uses the Twig third-party library for content templating and sanitization. Twig has released a security update 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.
- If you are using Drupal 9.3, update to Drupal 9.3.22.
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.
Drupal 7 core does not include Twig and therefore is not affected.
Reported By: Fixed By:- xjm of the Drupal Security Team
- Alex Pott of the Drupal Security Team
- Sascha Grossenbacher
- Lee Rowlands of the Drupal Security Team
- Lauri Eskola, provisional member of the Drupal Security Team
- Nathaniel Catchpole of the Drupal Security Team
- Dave Long, provisional member of the Drupal Security Team
- cilefen of the Drupal Security Team
- James Williams
- Benji Fisher, provisional member of the Drupal Security Team
Permissions by Term - Moderately critical - Access bypass - SA-CONTRIB-2022-056
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
- federico prato
- Peter Majmesku
- Jess of the Drupal Security Team
- Damien McKenna of the Drupal Security Team
- Greg Knaddison of the Drupal Security Team
Permissions by Term - Moderately critical - Access bypass - SA-CONTRIB-2022-055
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
- Peter Majmesku
- ytsurk
- Joseph
- Julian Pustkuchen
- Aleksi Peebles
- Ambient.Impact
- Stephen Mustgrave
- Jay McGraw
- Damien McKenna of the Drupal Security Team
- Greg Knaddison of the Drupal Security Team
Next.js - Moderately critical - Access bypass - SA-CONTRIB-2022-054
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:
- Upgrade to version v1.3.0.
- 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.
Reported By: Fixed By: Coordinated By:- Damien McKenna of the Drupal Security Team
Commerce Elavon - Moderately critical - Access bypass - SA-CONTRIB-2022-053
This module enables you to accept payments from the Elavon payment provider.
The module doesn't sufficiently verify that it's communicating with the correct server when using the Elavon (On-site) payment gateway, which could lead to leaking valid payment details as well as accepting invalid payment details.
This vulnerability is mitigated by the fact that an attacker must be able to spoof the Elavon DNS received by your site.
Solution:Install the latest version:
- If you use the Commerce Elavon module for Drupal 8.x/9.x, upgrade to Commerce Elavon 8.x-2.3
- If you use the Commerce Elavon module version 1.x for Drupal 7.x, upgrade to Commerce Elavon 7.x-1.5
- Andy Fowlston
- Greg Knaddison of the Drupal Security Team
- Damien McKenna of the Drupal Security Team
- Greg Knaddison of the Drupal Security Team
jQuery UI Checkboxradio - Moderately critical - Cross site scripting - SA-CONTRIB-2022-052
jQuery UI is a third-party library used by Drupal. The jQuery UI Checkboxradio module provides the jQuery UI Checkboxradio library (which was previously in Drupal 8 core, but has since been removed from core and moved to this module).
As part of the jQuery UI 1.13.2 update, the jQuery UI project disclosed following security issue that may affect sites using the jQuery UI Checkboxradio module:
Solution:Install the latest version. If you use the jQuery UI Checkboxradio module for Drupal 9, upgrade to:
Reported By:- Benji Fisher, provisional member of the Drupal Security Team
- Benji Fisher, provisional member of the Drupal Security Team
- xjm of the Drupal Security Team
- Lauri Eskola, provisional member of the Drupal Security Team
- Greg Knaddison of the Drupal Security Team
- xjm of the Drupal Security Team
Tagify - Moderately critical - Access bypass - SA-CONTRIB-2022-051
This module provides a widget to transform entity reference fields into a more user-friendly tags input component with a great performance.
The module doesn't sufficiently check access for the add operation. Users with permission to edit content can view and reference unpublished terms. The edit form may expose term data that users could not otherwise see, since there is no term view route by default.
This vulnerability is slightly mitigated by the fact that an attacker must have a role with the permission "access content", so may not be accessible to anonymous users on all sites.
Solution:Install the latest version:
- If you use the Tagify module for Drupal 9.x, upgrade to Tagify 1.0.5
- Damien McKenna of the Drupal Security Team
- Greg Knaddison of the Drupal Security Team
PDF generator API - Moderately critical - Remote Code Execution - SA-CONTRIB-2022-050
This module enables you to generate PDF versions of content.
Some installations of the module make use of the dompdf/dompdf third-party dependency.
Security vulnerabilities exist for versions of dompdf/dompdf before 2.0.0 as described in the 2.0.0 release notes.
Solution:Install the latest version:
- If you use the pdf_api module for Drupal 2.x, upgrade to pdf_api 2.2.2
- Damien McKenna of the Drupal Security Team
- Greg Knaddison of the Drupal Security Team
Context - Moderately critical - Cross Site Scripting - SA-CONTRIB-2022-049
This module enables you to conditionally display blocks in particular theme regions.
The module doesn't sufficiently sanitize the title of a block as displayed in the admin UI when a site administrator edits a context block reaction.
This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer blocks".
Solution:Install the latest version:
- If you use the Context module for Drupal 7.x, upgrade to Context 7.x-3.11.
- Damien McKenna of the Drupal Security Team
- Greg Knaddison of the Drupal Security Team
- Michael Hess of the Drupal Security Team
Drupal core - Moderately critical - Multiple vulnerabilities - SA-CORE-2022-015
The Media oEmbed iframe route does not properly validate the iframe domain setting, which allows embeds to be displayed in the context of the primary domain. Under certain circumstances, this could lead to cross-site scripting, leaked cookies, or other vulnerabilities.
This advisory is not covered by Drupal Steward.
Solution:Install the latest version:
- If you are using Drupal 9.4, update to Drupal 9.4.3.
- If you are using Drupal 9.3, update to Drupal 9.3.19.
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.
Drupal 7 core does not include the Media module and therefore is not affected.
Reported By:- Heine of the Drupal Security Team
- Lee Rowlands of the Drupal Security Team
- Alex Pott of the Drupal Security Team
- Samuel Mortenson
- xjm of the Drupal Security Team
- Heine of the Drupal Security Team
- Joseph Zhao, provisional member of the Drupal Security Team
- Vijay Mani, provisional member of the Drupal Security Team
- Alex Bronstein of the Drupal Security Team
- Neil Drumm of the Drupal Security Team
- Benji Fisher, provisional member of the Drupal Security Team
- Jen Lampton, provisional member of the Drupal Security Team
- Dave Long, provisional member of the Drupal Security Team
Drupal core - Critical - Arbitrary PHP code execution - SA-CORE-2022-014
Drupal core sanitizes filenames with dangerous extensions upon upload (reference: SA-CORE-2020-012) and strips leading and trailing dots from filenames to prevent uploading server configuration files (reference: SA-CORE-2019-010).
However, the protections for these two vulnerabilities previously did not work correctly together. As a result, if the site were configured to allow the upload of files with an htaccess extension, these files' filenames would not be properly sanitized. This could allow bypassing the protections provided by Drupal core's default .htaccess files and possible remote code execution.
This issue is mitigated by the fact that it requires a field administrator to explicitly configure a file field to allow htaccess as an extension (a restricted permission), or a contributed module or custom code that overrides allowed file uploads.
Solution:Install the latest version:
- If you are using Drupal 9.4, update to Drupal 9.4.3.
- If you are using Drupal 9.3, update to Drupal 9.3.19.
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.
Drupal 7 core is not affected.
Auditing your files directory's .htaccess to ensure it has not been overwritten or overridden in a subdirectoryIf your web server uses Apache httpd with AllowOverride, you should check within your files directories and subdirectories to ensure that any .htaccess files present are intentional. You can search for files named .htaccess by running the following command in the roots of both your public and private files directory:
find ./ -name ".htaccess" -print
Drupal automatically creates .htaccess files like the following in the root of the public files directory:
# Turn off all options we don't need. Options -Indexes -ExecCGI -Includes -MultiViews # Set the catch-all handler to prevent scripts from being executed. SetHandler Drupal_Security_Do_Not_Remove_See_SA_2006_006 <Files *> # Override the handler again if we're run later in the evaluation list. SetHandler Drupal_Security_Do_Not_Remove_See_SA_2013_003 </Files> # If we know how to do it safely, disable the PHP engine entirely. <IfModule mod_php7.c> php_flag engine off </IfModule> <IfModule mod_php.c> php_flag engine off </IfModule>Check with your system administrator for the correct .htaccess configuration for the given files directory.
This advisory is not covered by Drupal Steward.
Reported By: Fixed By:- Peter Wolanin of the Drupal Security Team
- xjm of the Drupal Security Team
- Drew Webber of the Drupal Security Team
- Alex Bronstein of the Drupal Security Team
- Greg Knaddison of the Drupal Security Team
- Jen Lampton, provisional member of the Drupal Security Team
- Lee Rowlands of the Drupal Security Team
- Dave Long, provisional member of the Drupal Security Team
Drupal core - Moderately critical - Access Bypass - SA-CORE-2022-013
Under certain circumstances, the Drupal core form API evaluates form element access incorrectly. This may lead to a user being able to alter data they should not have access to.
No forms provided by Drupal core are known to be vulnerable. However, forms added through contributed or custom modules or themes may be affected.
This advisory is not covered by Drupal Steward.
Solution:Install the latest version:
- If you are using Drupal 9.4, update to Drupal 9.4.3.
- If you are using Drupal 9.3, update to Drupal 9.3.19.
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.
Drupal 7 core is not affected.
Reported By: Fixed By:- Pierre Rudloff
- Tim Plunkett
- Heine of the Drupal Security Team
- Alex Bronstein of the Drupal Security Team
- xjm of the Drupal Security Team
- Lauri Eskola, provisional member of the Drupal Security Team
- Dave Long, provisional member of the Drupal Security Team
- Lee Rowlands of the Drupal Security Team
Drupal core - Moderately critical - Information Disclosure - SA-CORE-2022-012
In some situations, the Image module does not correctly check access to image files not stored in the standard public files directory when generating derivative images using the image styles system.
Access to a non-public file is checked only if it is stored in the "private" file system. However, some contributed modules provide additional file systems, or schemes, which may lead to this vulnerability.
This vulnerability is mitigated by the fact that it only applies when the site sets (Drupal 9) $config['image.settings']['allow_insecure_derivatives'] or (Drupal 7) $conf['image_allow_insecure_derivatives'] to TRUE. The recommended and default setting is FALSE, and Drupal core does not provide a way to change that in the admin UI.
Some sites may require configuration changes following this security release. Review the release notes for your Drupal version if you have issues accessing files or image styles after updating.
Solution:Install the latest version:
- If you are using Drupal 9.4, update to Drupal 9.4.3.
- If you are using Drupal 9.3, update to Drupal 9.3.19.
- If you are using Drupal 7, update to Drupal 7.91.
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.
Reported By: Fixed By:- Lee Rowlands of the Drupal Security Team
- Conrad Lara
- mondrake
- Alex Bronstein of the Drupal Security Team
- Dave Reid of the Drupal Security Team
- xjm of the Drupal Security Team
- Guy Elsmore-Paddock
- Dave Long Provisional Member of the Drupal Security Team
- Lauri Eskola Provisional Member of the Drupal Security Team
- David Strauss of the Drupal Security Team
- Benji Fisher Provisional Member of the Drupal Security Team
- Alex Pott of the Drupal Security Team
- Drew Webber of the Drupal Security Team
- Fabian Franz
Entity Print - Moderately critical - Multiple: Remote Code Execution, Information disclosure - SA-CONTRIB-2022-048
This module enables you to generate print versions of content.
Some installations of the module make use of the dompdf/dompdf third-party dependency.
Security vulnerabilities exist for versions of dompdf/dompdf < 2.0.0
See the library release notes for more detail: https://github.com/dompdf/dompdf/releases/tag/v2.0.0
Note on 3rd party vulnerabilitiesThis security advisory corresponds to a 3rd party vulnerability. Normally the Drupal Security Team would not issue advisories related to 3rd party code that is shipped separately from a module per our policy (most recent update is PSA-2019-09-04). In this case, because the module required a specific version and could not be updated without a change to the Drupal module we do issue an advisory.
Solution:Install the latest version (8.x-2.6) of this module and update dompdf/dompdf at the same time. It is recommended to use composer to do the update using commands similar to the following:
composer update drupal/entity_printcomposer require dompdf/dompdf:~2 Reported By: Fixed By:
- Lee Rowlands of the Drupal Security Team
- Carlos Santana
- Manoj Selvan
- Lee Rowlands of the Drupal Security Team
- Greg Knaddison of the Drupal Security Team
Config Terms - Critical - Access bypass - SA-CONTRIB-2022-047
This module enables you to create and manage a version of taxonomy based on configuration entities instead of content. This allows the terms, vocabularies, and their structure to be exported, imported, and managed as site configuration.
The module doesn't sufficiently check access for the edit and delete operations. Users with "access content" permission can edit or delete any term. The edit form may expose term data that users could not otherwise see, since there is no term view route by default.
This vulnerability is slightly mitigated by the fact that an attacker must have a role with the permission "access content", so may not be accessible to anonymous users on all sites.
Solution:Install the latest version:
- If you use the Config Terms module for Drupal 9.x, upgrade to Config Terms 8.x-1.6 or later
Lottiefiles Field - Moderately critical - Cross Site Scripting - SA-CONTRIB-2022-046
The Lottiefiles Field module enables you to integrate the lottiefiles features into your page.
The module does not sufficiently filter user-provided text on output, resulting in a Cross-Site Scripting (XSS) vulnerability.
This vulnerability is mitigated by the fact that an attacker must have a role with the permission to create or edit content that has lottiefiles fields.
Solution:Install the latest version:
- If you use the lottifiles_field module for Drupal 8.x or 9.x, upgrade to Lottiefiles Field 1.0.3.
- Greg Knaddison of the Drupal Security Team
Drupal core - Moderately critical - Third-party libraries - SA-CORE-2022-011
Drupal uses the third-party Guzzle library for handling HTTP requests and responses to external services. Guzzle has released two security advisories:
- Failure to strip the Cookie header on change in host or HTTP downgrade
- Fix failure to strip Authorization header on HTTP downgrade
These do not affect Drupal core, but may affect some contributed projects or custom code on Drupal sites.
We are issuing this security advisory outside our regular Drupal security release window schedule since Guzzle has already published information about the vulnerabilities, and vulnerabilities might exist in contributed modules or custom modules that use Guzzle for outgoing requests. Guzzle has rated these vulnerabilities as high-risk.
This advisory is not covered by Drupal Steward.
Solution:Install the latest version:
- If you are using Drupal 9.4, update to Drupal 9.4.0-rc2.
- If you are using Drupal 9.3, update to Drupal 9.3.16.
- If you are using Drupal 9.2, update to Drupal 9.2.21.
All versions of Drupal 9 prior to 9.2.x are end-of-life and do not receive security coverage. Note that Drupal 8 has reached its end of life.
Drupal 7 is not affected.
Reported By: Fixed By:- Heine of the Drupal Security Team
- Dave Long, provisional member of the Drupal Security Team
- Damien McKenna of the Drupal Security Team
- Michael Hess of the Drupal Security Team
- cilefen of the Drupal Security Team
- xjm of the Drupal Security Team
- Benji Fisher, provisional member of the Drupal Security Team
