View online: https://www.drupal.org/sa-contrib-2018-056
Project: File (Field) Paths [1]
Date: 2018-August-15
Security risk: *Critical* 15∕25
AC:Basic/A:User/CI:Some/II:All/E:Theoretical/TD:Default [2]
Vulnerability: Remote Code Execution
Description:
This module enables you to automatically sort and rename your uploaded files
using token based replacement patterns to maintain a nice clean filesystem.
The module doesn't sufficiently sanitize the path while a new file is
uploading, allowing a remote attacker to execute arbitrary PHP code.
This vulnerability is mitigated by the fact that an attacker must have access
to a form containing a widget processed by this module.
Solution:
Install the latest version:
* If you use the filefield_paths module for Drupal 7.x, upgrade to
filefield_paths 7.x-1.1 [3]
Reported By:
* Wayne Eaker [4]
Fixed By:
* Oleh Vehera [5]
Coordinated By:
* Michael Hess [6] of the Drupal Security Team
[1] https://www.drupal.org/project/filefield_paths
[2] https://www.drupal.org/security-team/risk-levels
[3] https://www.drupal.org/project/filefield_paths/releases/7.x-1.1
[4] https://www.drupal.org/user/326925
[5] https://www.drupal.org/user/3260314
[6] https://www.drupal.org/u/mlhess
View online: https://www.drupal.org/sa-contrib-2018-055
Project: PHP Configuration [1]
Version: 8.x-1.07.x-1.0
Date: 2018-August-08
Security risk: *Critical* 17∕25
AC:Basic/A:Admin/CI:All/II:All/E:Theoretical/TD:All [2]
Vulnerability: Arbitrary PHP code execution
Description:
This module enables you to add or overwrite PHP configuration on a drupal
website.
The module doesn't sufficiently allow access to set these configurations,
leading to arbitrary PHP configuration execution by an attacker.
This vulnerability is mitigated by the fact that an attacker must have a role
with the permission "administer phpconfig".
After updating the module, it's important to review the permissions of your
website and if 'administer phpconfig' permission is given to a not fully
trusted user role, we advise to revoke it.
Solution:
Install the latest version:
* If you use the PHP Configuration module for Drupal 7.x, upgrade to
PHP Configuration
7.x-1.1
* If you use the PHP Configuration module for Drupal 8.x, upgrade to
PHP Configuration
8.x-1.1
Also see the PHP Configuration [3] project page.
Reported By:
* Balazs Janos Tatar [4] Provisional security team member
Fixed By:
* bappa.sarkar [5] The module maintainer
Coordinated By:
* mpotter [6] of the Drupal Security Team
[1] https://www.drupal.org/project/phpconfig
[2] https://www.drupal.org/security-team/risk-levels
[3] https://www.drupal.org/project/phpconfig
[4] https://www.drupal.org/u/tatarbj
[5] https://www.drupal.org/user/262655
[6] https://www.drupal.org/u/mpotter
View online: https://www.drupal.org/SA-CORE-2018-005
* Advisory ID: SA-CORE-2018-005
* Project: Drupal core [1]
* Version: 8.x
* CVE: CVE-2018-14773
* Date: 2018-August-01
-------- DESCRIPTION
---------------------------------------------------------
The Drupal project uses the Symfony library. The Symfony library has released
a security update that impacts Drupal. Refer to the Symfony security
advisory for the issue [2].
The same vulnerability also exists in the Zend Feed and Diactoros libraries
included in Drupal core; however, Drupal core does not use the vulnerable
functionality. If your site or module uses Zend Feed or Diactoros directly,
read the Zend Framework security advisory [3] and update or patch as needed.
The Drupal Security Team would like to to thank the Symfony and Zend Security
teams for their collaboration on this issue.
-------- VERSIONS AFFECTED
---------------------------------------------------
8.x versions before 8.5.6.
-------- SOLUTION
------------------------------------------------------------
Upgrade to Drupal 8.5.6.
Versions of Drupal 8 prior to 8.5.x are end-of-life and do not receive
security coverage.
-------- CONTACT AND MORE INFORMATION
----------------------------------------
The Drupal security team can be reached at security at drupal.org or via the
contact form at https://www.drupal.org/contact [4].
Learn more about the Drupal Security team and their policies [5], writing
secure code for Drupal [6], and securing your site [7].
Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [8]
[1] https://www.drupal.org/project/drupal
[2] https://symfony.com/cve-2018-14773
[3] https://framework.zend.com/security/advisory/ZF2018-01
[4] https://www.drupal.org/contact
[5] https://www.drupal.org/security-team
[6] https://www.drupal.org/writing-secure-code
[7] https://www.drupal.org/security/secure-configuration
[8] https://twitter.com/drupalsecurity