GHSA-q3hq-hm5h-qrx3 CVE-2022-43691
Concrete CMS vulnerable to Cleartext Transmission of Sensitive Information
- Severity
- 5.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.48%
- Chance of exploitation in the next 30 days. Higher than 41.62% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-319 Cleartext Transmission of Sensitive Information
- Fix
8.5.10- Upgrade concrete5/concrete5 to this version or later
Description
Concrete CMS (formerly concrete5) below 8.5.10 and between 9.0.0 and 9.1.2 inadvertently disclose server-side sensitive information (secrets in environment variables and server information) when Debug Mode is left on in production.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| concrete5/concrete5 | < 8.5.10 |
8.5.10 |
| concrete5/concrete5 | >= 9.0.0, < 9.1.3 |
9.1.3 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
concrete5/concrete5 Packagist → 8.5.10
- composer
composer require concrete5/concrete5:^8.5.10
Severity breakdown
CVSS 3.1 5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Weakness
CWE-319: Cleartext Transmission of Sensitive Information
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
How to prevent it
- Architecture and Design: Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
- Implementation: When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
- Implementation: When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
- Testing: Use tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session. These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.
- Operation: Configure servers to use encrypted channels for communication, which may include SSL or other secure protocols.
References
Advisories
Packages
Other links
- documentation.concretecms.org/developers/introduction/version-history/8510-release-notes
- documentation.concretecms.org/developers/introduction/version-history/913-release-notes
- github.com/concretecms/concretecms/releases/8.5.10
- github.com/concretecms/concretecms/releases/9.1.3
- concretecms.org/about/project-news/security/concrete-cms-security-advisory-2022-10-31
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-g82f-9pw7-773w Concrete CMS: PHP Object Injection via unserialize() calls | High | Also affects concrete5/concrete5 |
| GHSA-52pr-7vmf-2w7x Concrete CMS is vulnerable to PHP Object Injection via unserialize() calls in the Workflow, Form block, and File/Set components | High | Also affects concrete5/concrete5 |
| GHSA-q9fm-mpg8-8jqm Concrete CMS is vulnerable to Stored XSS via page name in the Atomik theme | Medium | Also affects concrete5/concrete5 |
| GHSA-jqvq-gv67-3567 Concrete CMS is vulnerable to IDOR + wrong-authorization-level in the Express association Reorder dialog | Medium | Also affects concrete5/concrete5 |
| GHSA-xjg6-5v39-v7fc Concrete CMS is vulnerable to CSRF via Backend\File::approveVersion | Medium | Also affects concrete5/concrete5 |
| GHSA-44q4-354f-c826 Concrete CMS is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/backend/file approveVersion() | Medium | Also affects concrete5/concrete5 |
| GHSA-6qjh-p324-694f Concrete CMS is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/backend/file rescanMultiple() | High | Also affects concrete5/concrete5 |
| GHSA-6fxm-r8p3-mx5c Concrete CMS is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/backend/file rescan() | High | Also affects concrete5/concrete5 |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor