HighGHSA-xx4r-5265-48j6
silverstripe/framework SQL injection in full text search
Published 27 May 2024 · Updated 2 Dec 2024
Affected packages
silverstripe/frameworkComposer
- Affected
- >=3.5.0-rc1 <3.5.6
- Fixed in
- 3.5.6
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^3.5.6silverstripe/frameworkComposer
- Affected
- >=3.6.0-rc1 <3.6.3
- Fixed in
- 3.6.3
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^3.6.3silverstripe/frameworkComposer
- Affected
- >=4.0.0-rc1 <4.0.1
- Fixed in
- 4.0.1
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^4.0.1Details
When performing a fulltext search in SilverStripe 4.0.0 the 'start' querystring parameter is never escaped safely. This exposes a possible SQL injection vulnerability.
The issue exists in 3.5 and 3.6 but is less vulnerable, as SearchForm sanitises these variables prior to passing to mysql.
Is GHSA-xx4r-5265-48j6 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/099a5a3c2d99ed39bdd8815e1e2790bb9351770b
- Linkgithub.com/silverstripe/silverstripe-framework/commit/a8465900bdc77199176c953890ce7587045b1ea4
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2017-008-1.yaml
- Packagegithub.com/silverstripe/silverstripe-framework
- Linkwww.silverstripe.org/download/security-releases/ss-2017-008
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.