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.
References
Link | Resource |
---|---|
http://www.securityfocus.com/bid/96919 | |
http://www.securitytracker.com/id/1038058 | |
https://www.drupal.org/SA-2017-001 | Release Notes Third Party Advisory |
http://www.securityfocus.com/bid/96919 | |
http://www.securitytracker.com/id/1038058 | |
https://www.drupal.org/SA-2017-001 | Release Notes Third Party Advisory |
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 03:29
Type | Values Removed | Values Added |
---|---|---|
References | () http://www.securityfocus.com/bid/96919 - | |
References | () http://www.securitytracker.com/id/1038058 - | |
References | () https://www.drupal.org/SA-2017-001 - Release Notes, Third Party Advisory |
Information
Published : 2017-03-16 14:59
Updated : 2024-11-21 03:29
NVD link : CVE-2017-6379
Mitre link : CVE-2017-6379
CVE.ORG link : CVE-2017-6379
JSON object : View
Products Affected
drupal
- drupal
CWE
CWE-352
Cross-Site Request Forgery (CSRF)