HighGHSA-gxxq-fhc7-3jv9CVE-2017-6379
Drupal Cross-Site Request Forgery (CSRF)
Published 17 May 2022 · Updated 23 Apr 2024
Affected packages
drupal/coreComposer
- Affected
- >=8.2.0 <8.2.7
- Fixed in
- 8.2.7
Update to the fixed version for your release line, for example:
composer require drupal/core:^8.2.7drupal/drupalComposer
- Affected
- >=8.2.0 <8.2.7
- Fixed in
- 8.2.7
Update to the fixed version for your release line, for example:
composer require drupal/drupal:^8.2.7Details
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.
Is GHSA-gxxq-fhc7-3jv9 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected drupal/core, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2017-6379
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/drupal/core/CVE-2017-6379.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/drupal/drupal/CVE-2017-6379.yaml
- Packagegithub.com/drupal/core
- Linkwww.drupal.org/SA-2017-001
- Linkwww.securityfocus.com/bid/96919
- Linkwww.securitytracker.com/id/1038058
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.