DrupalCMS
CVE-2017-6924
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 · uneditedIn Drupal 8 prior to 8.3.7; When using the REST API, users without the correct permission can post comments via REST that are approved even if the user does not have permission to post approved comments. This issue only affects sites that have the RESTful Web Services (rest) module enabled, the comment entity REST resource enabled, and where an attacker can access a user account on the site with permissions to post comments, or where anonymous users can post comments.
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 confidenceDrupal 8 prior to 8.3.7 contains an authorization bypass vulnerability in the RESTful Web Services module. When the comment entity REST resource is enabled, the API does not properly enforce the 'post approved comments' permission, allowing authenticated users or anonymous users with comment posting rights to create approved comments without having the required approval permission.
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.3.7CVSS 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
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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.
-
Check your Drupal 8 core versionNavigate to admin/reports/status or check the VERSION file in your Drupal root directory, or run: drush status | grep Drupal versionAffected if The installed version is 8.0.0 through 8.3.6 (versions less than 8.3.7)
-
Verify the RESTful Web Services module is enabledNavigate to admin/modules and look for RESTful Web Services (rest) in the list, or run: drush pm-list --type=module --status=enabled | grep restAffected if The RESTful Web Services (rest) module is enabled
-
Confirm the comment entity REST resource is enabledCheck admin/config/services/rest or look for the comment resource in your REST UI configuration, or inspect your rest.resources configuration fileAffected if The comment entity REST resource is enabled and exposed via REST API
-
Review comment-related permissionsNavigate to admin/people/permissions and locate the Comment section - check if authenticated or anonymous users have 'Post comments' permissionAffected if Authenticated users or anonymous users have the 'Post comments' permission AND the comment REST resource is exposed without proper approval permission enforcement
You are affected if running Drupal 8.0.0-8.3.6 with the RESTful Web Services module enabled and the comment entity REST resource exposed, allowing users to bypass the approval permission requirement.
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 data8.3.7
Update Drupal 8 to version 8.3.7 or later. Until updated, consider disabling the comment REST resource or restricting REST API access through authentication and firewall rules.
Fix this in Drupal
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6924 — 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-6924 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