CVE-2017-6381

Description

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

Category

8.1
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 5.38% Top 15%
Vendor Advisory drupal.org
Affected: Drupal Drupal Core
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2017-6381?
CVE-2017-6381 has been scored as a high severity vulnerability.
How to fix CVE-2017-6381?
To fix CVE-2017-6381, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-6381 being actively exploited in the wild?
It is possible that CVE-2017-6381 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~5% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-6381?
CVE-2017-6381 affects Drupal Drupal Core.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.