CVE-2020-9280: SilverStripe Folders migrated from 3.x may be unsafe to upload to
(updated )
In SilverStripe through 4.5, files uploaded via Forms to folders migrated from Silverstripe CMS 3.x may be put to the default “/Uploads” folder instead. This affects installations which allowed upload folder protection via the optional silverstripe/secureassets module under 3.x. This module is installed and enabled by default on the Common Web Platform (CWP). The vulnerability only affects files uploaded after an upgrade to 4.x.
References
- forum.silverstripe.org/c/releases
- github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/assets/CVE-2020-9280.yaml
- github.com/advisories/GHSA-592m-4533-rxq9
- github.com/silverstripe/silverstripe-assets/commit/6779fd3c8c1c05a3db5035bf6e541c9483d161fc
- github.com/silverstripe/silverstripe-framework
- github.com/silverstripe/silverstripe-userforms/commit/3bbad2044279ade5e5a5d0ae1822bafe479f8a26
- nvd.nist.gov/vuln/detail/CVE-2020-9280
- www.silverstripe.org/download/security-releases
- www.silverstripe.org/download/security-releases/cve-2020-9280
Code Behaviors & Features
Detect and mitigate CVE-2020-9280 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →