CVE-2017-6379
N/A
Published: March 16, 2017 at 02:00 PM UTC
Updated: June 17, 2026 at 01:22 AM UTC
1 product affected across 1 vendorDrupal
Using Drupal Core by Drupal?
Get instant alerts when new vulnerabilities affect Drupal Core - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.8%
Description
Some administrative paths in Drupal 8.2.x before 8.2.7 did not include protection for CSRF. This would allow an attacker to disable some blocks on a site. This issue is mitigated by the fact that users would have to know the block ID.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
8.2 ≤ v < 8.2.78.2.08.2.0 beta18.2.0 beta28.2.0 beta38.2.0 rc18.2.0 rc28.2.18.2.28.2.38.2.48.2.58.2.6
Affected range stops below 8.2.7, so it looks safe — our inference, not a vendor statement
Remediation
No guide yetNo remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.
References (3)
x_refsource_CONFIRMRelease NotesThird Party Advisory
Source: [email protected]
https://www.drupal.org/SA-2017-001Quick Info
StatusMODIFIED
CWE
CWE-352
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card