CVE-2017-6381

UnknownEPSS 3.90%

Last modified

CVE-2017-6381 is a vulnerability of currently unknown severity. 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. EPSS estimates a 3.90% chance of exploitation in the next 30 days.

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

Metrics

EPSS Probability
3.90%

88.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
DrupalDrupal8.0.0
DrupalDrupal8.0.1
DrupalDrupal8.0.2
DrupalDrupal8.0.3
DrupalDrupal8.0.4
DrupalDrupal8.0.5
DrupalDrupal8.0.6
DrupalDrupal8.1.0
DrupalDrupal8.1.1
DrupalDrupal8.1.2
DrupalDrupal8.1.3
DrupalDrupal8.1.4
DrupalDrupal8.1.5
DrupalDrupal8.1.6
DrupalDrupal8.1.7
DrupalDrupal8.1.8
DrupalDrupal8.1.9
DrupalDrupal8.1.10
DrupalDrupal8.2.0
DrupalDrupal8.2.1

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-6381?
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
How severe is CVE-2017-6381?
Severity scoring for CVE-2017-6381 is pending analysis. The EPSS model estimates a 3.90% probability of exploitation in the next 30 days.
How do I fix CVE-2017-6381?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-6381?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST