MediumGHSA-p7f6-8mcm-fwv3CVE-2024-52600
Statamic CMS has a Path Traversal in Asset Upload
Published 19 Nov 2024 · Updated 19 Nov 2024
Affected package
statamic/cmsComposer
- Affected
- <5.17.0
- Fixed in
- 5.17.0
Update to the fixed version for your release line, for example:
composer require statamic/cms:^5.17.0Details
Assets uploaded with appropriately crafted filenames may result in them being placed in a location different than what was configured.
Impact
- Affects front-end forms with
assetsfields. - Affects other places where assets can be uploaded, although users would need upload permissions anyway.
- Files can be uploaded so they would be located on the server in a different location, and potentially override existing files.
- Traversal _outside_ an asset container was not possible.
Patches
This has been fixed in 5.17.0.
Is GHSA-p7f6-8mcm-fwv3 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 statamic/cms, and gives you the command that fixes it.
References
- Linkgithub.com/statamic/cms/security/advisories/GHSA-p7f6-8mcm-fwv3
- Advisorynvd.nist.gov/vuln/detail/CVE-2024-52600
- Linkgithub.com/statamic/cms/commit/0c07c10009a2439c8ee56c8faefd1319dc6e388d
- Linkgithub.com/statamic/cms/commit/400875b20f40e1343699d536a432a6fc284346da
- Linkgithub.com/statamic/cms/commit/4cc2c9bd0f39a93b3fc7e9ef0f12792576fd380d
- Packagegithub.com/statamic/cms
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.