Drupal Cross-Site Request Forgery (CSRF)
Impact
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.
Source excerpt · OSVThis issue is mitigated by the fact that users would have to know the block ID.
Affected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
| Affected range | Recorded fix |
|---|---|
| From 8.2.0 before 8.2.7Ecosystem versions | 8.2.7 |
Version evidence: OSV · GHSA-gxxq-fhc7-3jv9
View original version evidence (7 explicit versions)
| Affected range | Recorded fix |
|---|---|
| From 8.2.0 before 8.2.7Ecosystem versions | 8.2.7 |
Version evidence: OSV · GHSA-gxxq-fhc7-3jv9
View original version evidence (7 explicit versions)
Original source 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.
References
- Security advisory nvd.nist.gov/vuln/detail/CVE-2017-6379
- Security advisory github.com/FriendsOfPHP/security-advisories/blob/master/drupal/core/CVE-2017-6379.yaml
- Security advisory github.com/FriendsOfPHP/security-advisories/blob/master/drupal/drupal/CVE-2017-6379.yaml
- Source reference github.com/drupal/core
- Source reference www.drupal.org/SA-2017-001
- Source reference www.securityfocus.com/bid/96919
- Source reference www.securitytracker.com/id/1038058