First published: Fri Nov 19 2021(Updated: )
Concrete CMS (formerly concrete5) versions below 8.5.7 has a SSRF mitigation bypass using DNS Rebind attack giving an attacker the ability to fetch cloud IAAS (ex AWS) IAM keys.To fix this Concrete CMS no longer allows downloads from the local network and specifies the validated IP when downloading rather than relying on DNS.Discoverer: Adrian Tiron from FORTBRIDGE ( https://www.fortbridge.co.uk/ )The Concrete CMS team gave this a CVSS 3.1 score of 3.5 AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N . Please note that Cloud IAAS provider mis-configurations are not Concrete CMS vulnerabilities. A mitigation for this vulnerability is to make sure that the IMDS configurations are according to a cloud provider's best practices.This 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-22969.
The severity of CVE-2021-22969 is medium with a CVSS score of 5.3.
CVE-2021-22969 is a vulnerability in Concrete CMS (formerly concrete5) versions below 8.5.7 that allows for a SSRF mitigation bypass using a DNS Rebind attack, enabling an attacker to fetch cloud IAAS (ex AWS) IAM keys.
To fix CVE-2021-22969, you need to upgrade Concrete CMS to version 8.5.7 or above, which includes a fix for this vulnerability.
You can find more information about CVE-2021-22969 in the official Concrete CMS documentation and the HackerOne report linked in the References section.