CVE-2017-6379

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.

Category

7.5
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.25%
Third-Party Advisory drupal.org
Affected: Drupal Drupal Core
Published at:
Updated at:

References

Link Tags
http://www.securitytracker.com/id/1038058 vdb entry
https://www.drupal.org/SA-2017-001 third party advisory release notes
http://www.securityfocus.com/bid/96919 vdb entry

Frequently Asked Questions

What is the severity of CVE-2017-6379?
CVE-2017-6379 has been scored as a high severity vulnerability.
How to fix CVE-2017-6379?
To fix CVE-2017-6379, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-6379 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2017-6379 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-6379?
CVE-2017-6379 affects Drupal Drupal Core.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.