silverstripe/framework code execution vulnerability
Published 27 May 2024 · Updated 2 Dec 2024
Affected packages
- Affected
- >=4.0.3-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
There is a vulnerability whereby arbitrary global functions may be executed if malicious user input is passed through to in the second argument of ViewableData::renderWith. This argument resolves associative arrays as template placeholders. This exploit requires that user code has been written which makes use of the second argument in renderWith and where user input is passed directly as a value in an associative array without sanitisation such as Convert::raw2xml().
ViewableData::customise is not vulnerable.
Is GHSA-vgxh-x8jv-hmff 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/6f50728b185e62c0087a58b295a015cb13276911
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2018-006-1.yaml
- Packagegithub.com/silverstripe/silverstripe-framework
- Linkwww.silverstripe.org/download/security-releases/ss-2018-006
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.