GHSA-f43j-8hq4-2xj9 json
silverstripe/framework uploaded PHP script execution in assets
published 2y ago modified last yr.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist silverstripe/framework 4.0.4, 4.1.1
Is GHSA-f43j-8hq4-2xj9 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | silverstripe/framework | >=4.0.0-rc1, <4.0.4 >=4.1.0-rc1, <4.1.1 |
4.0.4 4.1.1 |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
github.com
/silverstripe/silverstripe-framework/commit/5b7eca2b6327556e2d5ad31bb00511b187e5992a
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2018-012-1.yaml
web
-
github.com
/silverstripe/silverstripe-framework
package
-
silverstripe.org
/download/security-releases/ss-2018-012
web
Sources
- GitHub Advisory GHSA-f43j-8hq4-2xj9
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.