Drupal Remote code execution
Published 13 May 2022 · Updated 23 Apr 2024
Affected packages
- Affected
- >=8.0 <8.2.7
- Fixed in
- 8.2.7
composer require drupal/core:^8.2.7- Affected
- >=8.0 <8.2.7
- Fixed in
- 8.2.7
composer require drupal/drupal:^8.2.7Details
A 3rd party development library including with Drupal 8 development dependencies is vulnerable to remote code execution. This is mitigated by the default .htaccess protection against PHP execution, and the fact that Composer development dependencies aren't normal installed. You might be vulnerable to this if you are running a version of Drupal before 8.2.2. To be sure you aren't vulnerable, you can remove the <siteroot>/vendor/phpunit directory from your production deployments
Is GHSA-rhx9-3qf7-r3j7 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected drupal/core, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2017-6381
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/drupal/core/CVE-2017-6381.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/drupal/drupal/CVE-2017-6381.yaml
- Packagegithub.com/drupal/core
- Linkwww.drupal.org/SA-2017-001
- Linkwww.securityfocus.com/bid/96919
- Linkwww.securitytracker.com/id/1038058
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.