DrupalCMS
CVE-2017-6377
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 · uneditedWhen adding a private file via the editor in Drupal 8.2.x before 8.2.7, the editor will not correctly check access for the file being attached, resulting in an access bypass.
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 confidenceIn Drupal 8.2.x before 8.2.7, the editor's private file attachment functionality fails to perform proper access control checks, allowing authenticated users to potentially access private files they should not have permission to view. This is an access bypass vulnerability specific to files attached through the editor interface.
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.2.0= 8.2.1= 8.2.2= 8.2.3= 8.2.4= 8.2.5= 8.2.6CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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.
-
Identify Drupal core versionRun `drush status` or check the `VERSION` constant in Drupal's bootstrap.inc file, or look at the version reported in the Drupal administration dashboard under Reports > Status reportAffected if The installed version is 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, or 8.2.6
-
Confirm private file system is configuredNavigate to Configuration > Media > File system (admin/config/media/file-system) or check the 'file_private_path' setting in settings.phpAffected if A private file system path is configured and enabled
-
Verify editor module is enabledCheck if the CKEditor module is installed and enabled at admin/modules, or run `drush pm-list --status=enabled` to list enabled modulesAffected if The CKEditor or other text editor module is enabled
-
Check for text formats using the editor with file attachmentNavigate to Configuration > Text formats and editors (admin/config/content/formats) and inspect each format; verify if the editor is configured with file attachment capabilitiesAffected if A text format uses an editor (CKEditor) that has file or image attachment functionality enabled
You are affected if your Drupal core version is 8.2.0-8.2.6 AND you have a private file system configured AND the editor module with file attachment is enabled for any text format.
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 dataUpgrade Drupal core to version 8.2.7 or later. If immediate upgrading is not possible, review and restrict editor permissions for private file management until the patch can be applied.
Fix this in Drupal
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6377 — 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-6377 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