Drupal

Project: Drupal coreDate: 2021-January-20Security risk: Critical 18∕25 AC:Complex/A:User/CI:All/II:All/E:Exploit/TD:UncommonVulnerability: Third-party librariesDescription: 

The Drupal project uses the pear Archive_Tar library, which has released a security update that impacts Drupal. For more information please see:

• CVE-2020-36193

Exploits may be possible if Drupal is configured to allow .tar, .tar.gz, .bz2, or .tlz file uploads and processes them.

Solution: 

Install the latest version:

• If you are using Drupal 9.1, update to Drupal 9.1.3.
• If you are using Drupal 9.0, update to Drupal 9.0.11.
• If you are using Drupal 8.9, update to Drupal 8.9.13.
• If you are using Drupal 7, update to Drupal 7.78.

Versions of Drupal 8 prior to 8.9.x are end-of-life and do not receive security coverage.

Disable uploads of .tar, .tar.gz, .bz2, or .tlz files to mitigate the vulnerability.

Reported By: 

• Richard Sheppard
• Stephen Cross
• Jonathan Danaher
• Kim Pepper

Fixed By: 

• Lee Rowlands of the Drupal Security Team
• Drew Webber of the Drupal Security Team
• Greg Knaddison of the Drupal Security Team
• Vijay Mani Provisional Member of the Drupal Security Team
• Jess of the Drupal Security Team
• Michael Hess of the Drupal Security Team

Project: Drupal coreDate: 2020-November-25Security risk: Critical 18∕25 AC:Complex/A:User/CI:All/II:All/E:Exploit/TD:UncommonVulnerability: Arbitrary PHP code executionCVE IDs: CVE-2020-28949CVE-2020-28948Description: 

The Drupal project uses the PEAR Archive_Tar library. The PEAR Archive_Tar library has released a security update that impacts Drupal. For more information please see:

• CVE-2020-28948
• CVE-2020-28949

Multiple vulnerabilities are possible if Drupal is configured to allow .tar, .tar.gz, .bz2, or .tlz file uploads and processes them.

To mitigate this issue, prevent untrusted users from uploading .tar, .tar.gz, .bz2, or .tlz files.

This is a different issue than SA-CORE-2019-012. Similar configuration changes may mitigate the problem until you are able to patch.

Solution: 

Install the latest version:

• If you are using Drupal 9.0, update to Drupal 9.0.9
• If you are using Drupal 8.9, update to Drupal 8.9.10
• If you are using Drupal 8.8 or earlier, update to Drupal 8.8.12
• If you are using Drupal 7, update to Drupal 7.75

Versions of Drupal 8 prior to 8.8.x are end-of-life and do not receive security coverage.

According to the regular security release window schedule, November 25th would not typically be a core security window. However, this release is necessary because there are known exploits for one of core's dependencies and some configurations of Drupal are vulnerable.

Reported By: 

• Luke Stewart

Fixed By: 

• Jess of the Drupal Security Team
• Drew Webber of the Drupal Security Team
• Michael Hess of the Drupal Security Team
• Neil Drumm of the Drupal Security Team
• Lee Rowlands of the Drupal Security Team

Project: Drupal coreDate: 2020-November-18Security risk: Critical 17∕25 AC:Basic/A:User/CI:All/II:All/E:Theoretical/TD:DefaultVulnerability: Remote code executionCVE IDs: CVE-2020-13671Description: 

Update November 18: Documented longer list of dangerous file extensions

Drupal core does not properly sanitize certain filenames on uploaded files, which can lead to files being interpreted as the incorrect extension and served as the wrong MIME type or executed as PHP for certain hosting configurations.

Solution: 

Install the latest version:

• If you are using Drupal 9.0, update to Drupal 9.0.8
• If you are using Drupal 8.9, update to Drupal 8.9.9
• If you are using Drupal 8.8 or earlier, update to Drupal 8.8.11
• If you are using Drupal 7, update to Drupal 7.74

Versions of Drupal 8 prior to 8.8.x are end-of-life and do not receive security coverage.

Additionally, it's recommended that you audit all previously uploaded files to check for malicious extensions. Look specifically for files that include more than one extension, like filename.php.txt or filename.html.gif, without an underscore (_) in the extension. Pay specific attention to the following file extensions, which should be considered dangerous even when followed by one or more additional extensions:

• phar
• php
• pl
• py
• cgi
• asp
• js
• html
• htm
• phtml

This list is not exhaustive, so evaluate security concerns for other unmunged extensions on a case-by-case basis.

Reported By: 

• ufku
• Mark Ferree
• Frédéric G. Marand
• Samuel Mortenson of the Drupal Security Team
• Derek Wright

Fixed By: 

• Heine of the Drupal Security Team
• ufku
• Mark Ferree
• Michael Hess of the Drupal Security Team
• David Rothstein of the Drupal Security Team
• Peter Wolanin of the Drupal Security Team
• Jess of the Drupal Security Team
• Frédéric G. Marand
• Stefan Ruijsenaars
• David Snopek of the Drupal Security Team
• Rick Manelius
• David Strauss of the Drupal Security Team
• Samuel Mortenson of the Drupal Security Team
• Ted Bowman
• Alex Pott of the Drupal Security Team
• Derek Wright
• Lee Rowlands of the Drupal Security Team
• Kim Pepper
• Wim Leers
• Nate Lampton
• Drew Webber of the Drupal Security Team
• Fabian Franz
• Alex Bronstein of the Drupal Security Team
• Neil Drumm of the Drupal Security Team
• Joseph Zhao
• Ryan Aslett