MediumGHSA-x5w2-wcr8-9q45

Silverstripe Missing security check on dev/build/defaults

Published 23 May 2024 · Updated 28 Nov 2024

Affected packages

silverstripe/frameworkComposer

Affected: <3.1.17
Fixed in: 3.1.17

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

silverstripe/frameworkComposer

Affected: >=3.2.0 <3.2.2
Fixed in: 3.2.2

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

silverstripe/frameworkComposer

Affected: >=3.3.0-beta1 <3.3.0
Fixed in: 3.3.0

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

Details

The buildDefaults method on DevelopmentAdmin is missing a permission check.

In live mode, if you access /dev/build, you are requested to login first. However, if you access /dev/build/defaults, then the action is performed without any login check. This should be protected in the same way that /dev/build is. The buildDefaults view is requireDefaultRecords() on each DataObject class, and hence has the potential to modify database state. It also lists all modified tables, allowing attackers more insight into which modules are used, and how the database tables are structured.

Is GHSA-x5w2-wcr8-9q45 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.