DrupalCMS
CVE-2017-6381
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA remote code execution vulnerability exists in PHPUnit, a third-party PHP unit testing framework bundled with Drupal 8's development dependencies. The vulnerability is present in the vendor/phpunit directory shipped with Drupal 8 versions prior to 8.2.2. While production deployments typically exclude Composer development dependencies, misconfigurations or improper deployment practices may leave this exploitable code accessible.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
DrupalCMS
= 8.0.0= 8.0.1= 8.0.2= 8.0.3= 8.0.4= 8.0.5= 8.0.6= 8.1.0= 8.1.1= 8.1.2= 8.1.3= 8.1.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Drupal 8 versionRun 'drush status' or inspect the composer.lock file in the web root for the 'drupal/core' or 'drupal/drupal' version entryAffected if The installed Drupal version is 8.0.0 through 8.1.4 (inclusive)
-
Verify vendor/phpunit directory presenceInspect the web root for the existence of the vendor/phpunit directory by listing the contents of the vendor folder or checking the filesystem directlyAffected if The vendor/phpunit directory exists in the deployment
-
Confirm PHPUnit scripts are web-accessibleAttempt to access http://[yourdomain]/vendor/phpunit/phpunit/ by HTTP request, or inspect the .htaccess file in the vendor directory to determine if PHP execution is blockedAffected if The PHPUnit scripts are reachable via HTTP without being blocked by .htaccess restrictions
You are affected if your Drupal 8 installation is version 8.0.0-8.1.4 AND the vendor/phpunit directory is present and accessible in your production deployment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRemove the vendor/phpunit directory from production deployments and verify that .htaccess protections against PHP execution in the vendor directory are active.
Fix this in Drupal
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6381 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-6381 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data