Drupal Cross-Site Request Forgery (CSRF)
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2017-6379US | high7.5 | — | ||
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 b… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.securityfocus.com/bid/96919WEB
- http://www.securitytracker.com/id/1038058WEB
- https://github.com/FriendsOfPHP/security-advisories/blob/master/drupal/core/CVE-2017-6379.yamlWEB
- https://github.com/FriendsOfPHP/security-advisories/blob/master/drupal/drupal/CVE-2017-6379.yamlWEB
- https://github.com/drupal/corePACKAGE
- https://nvd.nist.gov/vuln/detail/CVE-2017-6379ADVISORY
- https://www.drupal.org/SA-2017-001WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan