HighGHSA-836p-6p4j-35cgCVE-2016-3164

Drupal Open Redirect

Published 17 May 2022 · Updated 3 Dec 2024

Affected packages

Affected
>=6.0 <6.38
Fixed in
6.38
Update to the fixed version for your release line, for example:composer require drupal/drupal:^6.38
Affected
>=7.0 <7.43
Fixed in
7.43
Update to the fixed version for your release line, for example:composer require drupal/drupal:^7.43
Affected
>=8.0 <8.0.4
Fixed in
8.0.4
Update to the fixed version for your release line, for example:composer require drupal/drupal:^8.0.4
drupal/coreComposer
Affected
>=8.0 <8.0.4
Fixed in
8.0.4
Update to the fixed version for your release line, for example:composer require drupal/core:^8.0.4
drupal/coreComposer
Affected
>=7.0 <7.43
Fixed in
7.43
Update to the fixed version for your release line, for example:composer require drupal/core:^7.43
drupal/coreComposer
Affected
>=6.0 <6.38
Fixed in
6.38
Update to the fixed version for your release line, for example:composer require drupal/core:^6.38

Details

Drupal 6.x before 6.38, 7.x before 7.43, and 8.x before 8.0.4 might allow remote attackers to conduct open redirect attacks by leveraging (1) custom code or (2) a form shown on a 404 error page, related to path manipulation.

Is GHSA-836p-6p4j-35cg 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/drupal, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.