Path traversal in Concrete CMS
Published 25 Jun 2022 · Updated 8 Nov 2023
Affected packages
- Affected
- >=9.0.0 <9.1.0
- Fixed in
- 9.1.0
composer require concrete5/core:^9.1.0- Affected
- <8.5.8
- Fixed in
- 8.5.8
composer require concrete5/core:^8.5.8Details
Concrete 8.5.7 and below as well as Concrete 9.0 through 9.0.2 allow traversal in /index.php/ccm/system/file/upload which could result in an Arbitrary File Delete exploit. This was remediated by sanitizing /index.php/ccm/system/file/upload to ensure Concrete doesn’t allow traversal and by changing isFullChunkFilePresent to have an early false return when input doesn't match expectations.Concrete CMS Security team ranked this 5.8 with CVSS v3.1 vector AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:N/A:H. Credit to Siebene for reporting.
Is GHSA-3jxh-6635-6jwp 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 concrete5/core, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2022-30117
- Linkhackerone.com/reports/1482280
- Linkdocumentation.concretecms.org/developers/introduction/version-history/858-release-notes
- Linkdocumentation.concretecms.org/developers/introduction/version-history/910-release-notes
- Packagegithub.com/concretecms/concretecms-core
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.