LowGHSA-6r58-4xgr-gm6mCVE-2019-12617
SilverStripe Priviledge escalation through cache pollution
Published 12 Nov 2019 · Updated 30 Nov 2024
Affected packages
silverstripe/frameworkComposer
- Affected
- >=4.4.0 <4.4.4
- Fixed in
- 4.4.4
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^4.4.4silverstripe/frameworkComposer
- Affected
- >=4.3.0 <4.3.5
- Fixed in
- 4.3.5
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^4.3.5Details
In SilverStripe through 4.3.3, there is access escalation for CMS users with limited access through permission cache pollution.
Is GHSA-6r58-4xgr-gm6m 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
- Advisorynvd.nist.gov/vuln/detail/CVE-2019-12617
- Linkforum.silverstripe.org/c/releases
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/CVE-2019-12617.yaml
- Linkwww.silverstripe.org/blog/tag/release
- Linkwww.silverstripe.org/download/security-releases
- Linkwww.silverstripe.org/download/security-releases/CVE-2019-12617
- Linkwww.silverstripe.org/download/security-releases/cve-2019-12617
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.