What is the severity of CVE-2017-6379?

CVE-2017-6379 is classified as a moderate severity vulnerability due to its potential impact on site administrative functions.

How do I fix CVE-2017-6379?

To fix CVE-2017-6379, upgrade Drupal to version 8.2.7 or later.

Which versions of Drupal are affected by CVE-2017-6379?

CVE-2017-6379 affects Drupal versions 8.2.0 to 8.2.6.

What can an attacker do with CVE-2017-6379?

An attacker could potentially disable administrative blocks on a site due to the lack of CSRF protection in certain admin paths.

Is there a workaround for CVE-2017-6379?

There are no specific workarounds; the recommended mitigation is to upgrade to a secure version of Drupal.

Vulnerability/
CVE-2017-6379

high

7.5

CWE

352

15/3/2017

16/3/2017

5/8/2024

CVE-2017-6379: CSRF

First published: Wed Mar 15 2017(Updated: )

Some admin paths were not protected with a CSRF token

Credit: mlhess@drupal.org mlhess@drupal.org

Affected Software	Affected Version	How to fix
composer/drupal/core	>=8.0<8.1.0>=8.1.0<8.2.0>=8.2.0<8.2.7
composer/drupal/drupal	>=8.0<8.1.0>=8.1.0<8.2.0>=8.2.0<8.2.7
Drupal Drupal	=8.2.0
Drupal Drupal	=8.2.0-beta1
Drupal Drupal	=8.2.0-beta2
Drupal Drupal	=8.2.0-beta3
Drupal Drupal	=8.2.0-rc1
Drupal Drupal	=8.2.0-rc2
Drupal Drupal	=8.2.1
Drupal Drupal	=8.2.2
Drupal Drupal	=8.2.3
Drupal Drupal	=8.2.4
Drupal Drupal	=8.2.5
Drupal Drupal	=8.2.6
composer/drupal/drupal	>=8.2.0<8.2.7	8.2.7
composer/drupal/core	>=8.2.0<8.2.7	8.2.7

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-6379?
CVE-2017-6379 is classified as a moderate severity vulnerability due to its potential impact on site administrative functions.
How do I fix CVE-2017-6379?
To fix CVE-2017-6379, upgrade Drupal to version 8.2.7 or later.
Which versions of Drupal are affected by CVE-2017-6379?
CVE-2017-6379 affects Drupal versions 8.2.0 to 8.2.6.
What can an attacker do with CVE-2017-6379?
An attacker could potentially disable administrative blocks on a site due to the lack of CSRF protection in certain admin paths.
Is there a workaround for CVE-2017-6379?
There are no specific workarounds; the recommended mitigation is to upgrade to a secure version of Drupal.

collector/friends-of-php
collector/nvd-index
agent/type
agent/first-publish-date
collector/github-advisory-latest
source/GitHub
alias/GHSA-gxxq-fhc7-3jv9
alias/CVE-2017-6379
agent/software-canonical-lookup
agent/weakness
agent/author
agent/severity
agent/references
agent/description
collector/nvd-cve
source/NVD
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/trending
agent/tags
agent/source
package-manager/composer
vendor/drupal
canonical/drupal drupal
version/drupal drupal/8.2.0
version/drupal drupal/8.2.0-beta1
version/drupal drupal/8.2.0-beta2
version/drupal drupal/8.2.0-beta3
version/drupal drupal/8.2.0-rc1
version/drupal drupal/8.2.0-rc2
version/drupal drupal/8.2.1
version/drupal drupal/8.2.2
version/drupal drupal/8.2.3
version/drupal drupal/8.2.4
version/drupal drupal/8.2.5
version/drupal drupal/8.2.6

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-6379?
CVE-2017-6379 is classified as a moderate severity vulnerability due to its potential impact on site administrative functions.
How do I fix CVE-2017-6379?
To fix CVE-2017-6379, upgrade Drupal to version 8.2.7 or later.
Which versions of Drupal are affected by CVE-2017-6379?
CVE-2017-6379 affects Drupal versions 8.2.0 to 8.2.6.
What can an attacker do with CVE-2017-6379?
An attacker could potentially disable administrative blocks on a site due to the lack of CSRF protection in certain admin paths.
Is there a workaround for CVE-2017-6379?
There are no specific workarounds; the recommended mitigation is to upgrade to a secure version of Drupal.