HighGHSA-vcg6-8fxc-x5cq

silverstripe/framework allows upload of dangerous file types

Published 27 May 2024 · Updated 2 Dec 2024

Affected packages

silverstripe/frameworkComposer

Affected: >=3.6.5-rc1 <3.6.6
Fixed in: 3.6.6

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

silverstripe/frameworkComposer

Affected: >=4.0.3-rc1 <4.0.4
Fixed in: 4.0.4

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

silverstripe/frameworkComposer

Affected: >=4.1.0-rc1 <4.1.1
Fixed in: 4.1.1

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

Details

Some potentially dangerous file types exist in File.allowed_extensions which could allow a malicious CMS user to upload files that then get executed in the security context of the website. We have removed the ability to upload .css, .js, .potm, .dotm, .xltm and .jar files in the default configuration. Since allowed_extensions are synced to webserver configuration (in assets/.htaccess) automatically, this will also deny access to any existing uploads with these extensions.

Review our security guidelines for the Common Web Platform and the File Security guide for SilverStripe 4 to find out how to add or remove extensions.

Is GHSA-vcg6-8fxc-x5cq 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.