First published: Fri Nov 19 2021(Updated: )
A bypass of adding remote files in Concrete CMS (previously concrete5) File Manager leads to remote code execution in Concrete CMS (concrete5) versions 8.5.6 and below.The external file upload feature stages files in the public directory even if they have disallowed file extensions. They are stored in a directory with a random name, but it's possible to stall the uploads and brute force the directory name. You have to be an admin with the ability to upload files, but this bug gives you the ability to upload restricted file types and execute them depending on server configuration.To fix this, a check for allowed file extensions was added before downloading files to a tmp directory.Concrete CMS Security Team gave this a CVSS v3.1 score of 5.4 AV:N/AC:H/PR:H/UI:R/S:C/C:N/I:H/A:NThis fix is also in Concrete version 9.0.0
Credit: support@hackerone.com
Affected Software | Affected Version | How to fix |
---|---|---|
Concretecms Concrete Cms | <8.5.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this vulnerability is CVE-2021-22968.
The severity level of CVE-2021-22968 is high, with a severity value of 7.2.
Concrete CMS (concrete5) versions 8.5.6 and below are affected by CVE-2021-22968.
CVE-2021-22968 allows bypassing file upload restrictions in Concrete CMS File Manager, leading to remote code execution.
Yes, you can find more information about CVE-2021-22968 in the Concrete CMS documentation and the HackerOne report.