MediumGHSA-g4hp-pfvf-vm5w

SilverStripe Vulnerability on 'isDev', 'isTest' and 'flush' $_GET validation

Published 23 May 2024 · Updated 28 Nov 2024

Affected packages

silverstripe/frameworkComposer

Affected: >=3.0.0 <3.0.14
Fixed in: 3.0.14

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.0.14

silverstripe/frameworkComposer

Affected: >=3.1.0 <3.1.13
Fixed in: 3.1.13

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.1.13

Details

When a secure token parameter is provided to a SilverStripe site (such as isDev or flush) an empty token parameter can be provided in order to bypass normal authentication parameters.

For instance, http://www.mysite.com/?isDev=1&isDevtoken will force a site to dev mode. Alternatively, "flush" could also be used in succession to cause excessive load on a victim site and risk denial of service.

The fix in this case is to ensure that empty tokens fail the validation check.

Is GHSA-g4hp-pfvf-vm5w 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 silverstripe/framework, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

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