silverstripe/framework uploaded PHP script execution in assets
Published 27 May 2024 · Updated 2 Dec 2024
Affected packages
- Affected
- >=4.0.0-rc1 <4.0.4
- Fixed in
- 4.0.4
composer require silverstripe/framework:^4.0.4- Affected
- >=4.1.0-rc1 <4.1.1
- Fixed in
- 4.1.1
composer require silverstripe/framework:^4.1.1Details
A weakness in the .htaccess rules preventing requests to uploaded PHP scripts allows PHP scripts that had made their way into the assets directory to be successfully executed through the use of a specially crafted URL. There are protections in place to disallow upload of PHP scripts through the CMS, meaning this weakness does not lead to direct vulnerabilities.
In addition, sites hosted on the New Zealand Common Web Platform or SilverStripe Platform have additional configuration in place which prevents PHP script execution in assets, even in a malicious party manages to upload these into the folder.
Is GHSA-f43j-8hq4-2xj9 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.
References
- Linkgithub.com/silverstripe/silverstripe-framework/commit/5b7eca2b6327556e2d5ad31bb00511b187e5992a
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2018-012-1.yaml
- Packagegithub.com/silverstripe/silverstripe-framework
- Linkwww.silverstripe.org/download/security-releases/ss-2018-012
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.