Drupal

Project: Drupal coreDate: 2019-February-20Security risk: Highly critical 23∕25 AC:None/A:None/CI:All/II:All/E:Exploit/TD:UncommonVulnerability: Remote Code ExecutionCVE IDs: CVE-2019-6340Description: 

Some field types do not properly sanitize data from non-form sources. This can lead to arbitrary PHP code execution in some cases.

A site is only affected by this if one of the following conditions is met:

• The site has the Drupal 8 core RESTful Web Services (rest) module enabled and allows GET, PATCH or POST requests, or
• the site has another web services module enabled, like JSON:API in Drupal 8, or Services or RESTful Web Services in Drupal 7.

(Note: The Drupal 7 Services module itself does not require an update at this time, but you should still apply other contributed updates associated with this advisory if Services is in use.)

Updates

• 2019-02-20: Updated risk score given new information; see PSA-2019-02-22. The security risk score has been updated to 23/25 as there are now known exploits in the wild. In addition, any enabled REST resource end-point, even if it only accepts GET requests, is also vulnerable. Note this does not include REST exports from Views module.

Solution: 

• If you are using Drupal 8.6.x, upgrade to Drupal 8.6.10.
• If you are using Drupal 8.5.x or earlier, upgrade to Drupal 8.5.11.
• Be sure to install any available security updates for contributed projects after updating Drupal core.
• No core update is required for Drupal 7, but several Drupal 7 contributed modules do require updates.

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

To immediately mitigate the vulnerability, you can disable all web services modules, or configure your web server(s) to not allow GET/PUT/PATCH/POST requests to web services resources. Note that web services resources may be available on multiple paths depending on the configuration of your server(s). For Drupal 7, resources are for example typically available via paths (clean URLs) and via arguments to the "q" query argument. For Drupal 8, paths may still function when prefixed with index.php/.

Reported By: 

• Samuel Mortenson of the Drupal Security Team

Fixed By: 

• Sascha Grossenbacher
• Peter Wolanin of the Drupal Security Team
• Samuel Mortenson of the Drupal Security Team
• Daniel Wehner
• Cash Williams of the Drupal Security Team
• Wim Leers
• Jess of the Drupal Security Team
• Lee Rowlands of the Drupal Security Team
• Alex Pott of the Drupal Security Team
• Francesco Placella
• Damian Lee
• Tobias Zimmermann
• Ted Bowman
• Damien McKenna of the Drupal Security Team
• Alex Bronstein of the Drupal Security Team
• Rob Loach
• Gabe Sullice
• Michael Hess of the Drupal Security Team
• Neil Drumm of the Drupal Security Team
• Heshan Wanigasooriya
• David Snopek of the Drupal Security Team
• Wolfgang Ziegler
• Miro Dietiker
• Truls S. Yggeseth

Project: Drupal coreDate: 2019-January-16Security risk: Critical 16∕25 AC:Complex/A:Admin/CI:All/II:All/E:Theoretical/TD:AllVulnerability: Arbitrary PHP code executionCVE IDs: CVE-2019-6339Description: 

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.
• If you are using Drupal 8.5.x or earlier, upgrade to Drupal 8.5.9.
• If you are using Drupal 7.x, upgrade to Drupal 7.62.

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

Known issues

This fix introduced a fatal error for some Drush installations when updating a site with Drush. New releases (8.6.7, 8.5.10, and 7.63) have been issued to resolve this regression. See the release notes for additional details.

Update information .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 of the Drupal Security Team
• Sam Thomas

Fixed By: 

• Cash Williams of the Drupal Security Team
• Lee Rowlands of the Drupal Security Team
• Samuel Mortenson of the Drupal Security Team
• Jess of the Drupal Security Team
• Alex Pott of the Drupal Security Team
• Ted Bowman
• Michael Hess of the Drupal Security Team
• Alex Bronstein of the Drupal Security Team
• Fabian Franz

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
• SA-CORE-2019-002

Updating to the latest Drupal core release will apply the fixes for all the above advisories.

Project: Drupal coreDate: 2019-January-16Security risk: Critical 16∕25 AC:Complex/A:User/CI:All/II:All/E:Proof/TD:UncommonVulnerability: Third Party Libraries CVE IDs: CVE-2019-6338Description: 

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 for details.

Solution: 

• If you are using Drupal 8.6.x, upgrade to Drupal 8.6.6.
• If you are using Drupal 8.5.x or earlier, upgrade to Drupal 8.5.9.
• If you are using Drupal 7.x, upgrade to Drupal 7.62.

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

Reported By: 

• Ayesh Karunaratne
• farisv

Fixed By: 

• Jess of the Drupal Security Team
• Ayesh Karunaratne
• michieltcs
• Lee Rowlands of the Drupal Security Team
• Alex Pott of the Drupal Security Team

Known issues

Users are reporting seeing a fatal error when updating their sites with Drush. Site owners may be able to run drush updb and either drush cc all or drush cr depending on the version to complete the update. Check the status report afterward to confirm that Drupal has been updated. See https://www.drupal.org/project/drupal/issues/3026386 for details.

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
• SA-CORE-2019-002

Updating to the latest Drupal core release will apply the fixes for all the above advisories.