Skip to content

GHSA-284f-f2hw-j2gx CVE-2021-22958

Server-Side Request Forgery vulnerability in concrete5

High Packagist
Severity
8.2 / 10
High · CVSS 3.1
Exploit chance (EPSS)
1.23%
Chance of exploitation in the next 30 days. Higher than 68.84% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-918 Server-Side Request Forgery (SSRF)
Fix
8.5.5
Upgrade concrete5/concrete5 to this version or later

Description

A Server-Side Request Forgery vulnerability was found in concrete5 < 8.5.5 that allowed a decimal notation encoded IP address to bypass the limitations in place for localhost allowing interaction with local services. Impact can vary depending on services exposed.

Affected versions

Packagist

PackageVulnerableFixed in
concrete5/concrete5
< 8.5.5
8.5.5

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.5

composer
composer require concrete5/concrete5:^8.5.5

Severity breakdown

CVSS 3.1 8.2

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

Weakness

CWE-918: Server-Side Request Forgery (SSRF)

The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy 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
Is this in your code?

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