HighGHSA-gm5x-hpmw-xpxgBIT-silverstripe-2020-6164CVE-2020-6164

Silverstripe CMS information disclosure

Published 24 May 2022 · Updated 22 May 2024

Affected packages

silverstripe/cmsComposer
Affected
<=4.5.0
Fixed in
No fix released
silverstripe/frameworkComposer
Affected
>=4.0.0 <4.4.7
Fixed in
4.4.7
Update to the fixed version for your release line, for example:composer require silverstripe/framework:^4.4.7
silverstripe/frameworkComposer
Affected
>=4.5.0 <4.5.4
Fixed in
4.5.4
Update to the fixed version for your release line, for example:composer require silverstripe/framework:^4.5.4

Details

In SilverStripe through 4.5.0, a specific URL path configured by default through the silverstripe/framework module can be used to disclose the fact that a domain is hosting a Silverstripe application. There is no disclosure of the specific version. The functionality on this URL path is limited to execution in a CLI context, and is not known to present a vulnerability through web-based access. As a side-effect, this preconfigured path also blocks the creation of other resources on this path (e.g. a page).

Is GHSA-gm5x-hpmw-xpxg 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/cms, and gives you the command that fixes it.

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

References

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