Drupal

Project: Drupal coreDate: 2022-September-28Security risk: Critical 18∕25 AC:Basic/A:Admin/CI:All/II:All/E:Proof/TD:AllVulnerability: Multiple vulnerabilitiesAffected versions: >= 8.0.0 <9.3.22 || >= 9.4.0 <9.4.7CVE IDs: CVE-2022-39261Description: 

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: 

• Fabien Potencier
• Nicolas Grekas
• James Williams

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

Project: Drupal coreDate: 2022-July-20Security risk: Moderately critical 11∕25 AC:Complex/A:User/CI:Some/II:Some/E:Theoretical/TD:UncommonVulnerability: Multiple vulnerabilitiesAffected versions: >= 8.0.0 <9.3.19 || >= 9.4.0 <9.4.3CVE IDs: CVE-2022-25276Description: 

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

Fixed By: 

• 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

Project: Drupal coreDate: 2022-July-20Security risk: Critical 15∕25 AC:Basic/A:Admin/CI:All/II:All/E:Theoretical/TD:UncommonVulnerability: Arbitrary PHP code executionAffected versions: >= 8.0.0 <9.3.19 || >= 9.4.0 <9.4.3CVE IDs: CVE-2022-25277Description: 

Updated 2022-07-20 19:45 UTC to indicate that this only affects Apache web servers.

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 on Apache web servers.

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 subdirectory

If 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: 

• Elar Lang

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

Project: Drupal coreDate: 2022-July-20Security risk: Moderately critical 12∕25 AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:UncommonVulnerability: Access BypassAffected versions: >= 8.0.0 <9.3.19 || >= 9.4.0 <9.4.3CVE IDs: CVE-2022-25278Description: 

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: 

• Pierre Rudloff

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

Project: Drupal coreDate: 2022-July-20Security risk: Moderately critical 13∕25 AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:UncommonVulnerability: Information DisclosureAffected versions: >=7.0 <7.91 || >= 8.0.0 <9.3.19 || >= 9.4.0 <9.4.3CVE IDs: CVE-2022-25275Description: 

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: 

• Guy Elsmore-Paddock
• Conrad Lara

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

Project: Drupal coreDate: 2022-June-10Security risk: Moderately critical 13∕25 AC:Complex/A:None/CI:Some/II:Some/E:Theoretical/TD:UncommonVulnerability: Third-party librariesAffected versions: >= 8.0.0 <9.2.21 || >= 9.3.0 <9.3.16CVE IDs: CVE-2022-31042CVE-2022-31043Description: 

Updated 22:00 UTC 2022-06-10: Added steps to update without drupal/core-recommended.

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.

Advanced users may also work around this issue by temporarily using drupal/core instead of drupal/core-recommended and then updating Guzzle to the desired version. More information on managing Guzzle with Drupal 9.4.

Reported By: 

• GHaddon
• Jeroen Tubex
• Yasen Ivanov

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