Skip to content

GHSA-m4mv-rmr7-h5f5 CVE-2023-2983

Pimcore Privilege Defined With Unsafe Actions vulnerability

High Packagist
Severity
6.5 / 10
High · CVSS 3.0
Exploit chance (EPSS)
0.92%
Chance of exploitation in the next 30 days. Higher than 60.26% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-267 Privilege Defined With Unsafe Actions
Fix
10.5.23
Upgrade pimcore/pimcore to this version or later

Description

Impact

A new user can privilege escalation to admin role which least config

Patches

Update to version 10.5.23 or apply this patches manually https://github.com/pimcore/pimcore/commit/c8f37b19c99cd82e4e558857d3e4d5476ea7228a.patch

Workarounds

Apply patches manually: https://github.com/pimcore/pimcore/commit/c8f37b19c99cd82e4e558857d3e4d5476ea7228a.patch

References

https://huntr.dev/bounties/6b2f33d3-2fd0-4d2d-ad7b-2c1e2417eeb1/

Affected versions

Packagist

PackageVulnerableFixed in
pimcore/pimcore
< 10.5.23
10.5.23

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.

pimcore/pimcore Packagist → 10.5.23

composer
composer require pimcore/pimcore:^10.5.23

Severity breakdown

CVSS 3.0 6.5

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

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

Weakness

CWE-267: Privilege Defined With Unsafe Actions

A particular privilege, role, capability, or right can be used to perform unsafe actions that were not intended, even when it is assigned to the correct entity.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design, Operation: Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-23rh-xw42-fq82
Pimcore: SQL Injection in Custom Reports via Malicious Report Configuration
High Also affects pimcore/pimcore
GHSA-9x44-4gxf-8c25
Pimcore Vulnerable to Remote Code Execution via DataObject Class-Definition Field Name
Critical Also affects pimcore/pimcore
GHSA-w23p-wrp7-ch38
Pimcore Hotspotimage getDataFromResource() unrestricted Serialize::unserialize over object-store column (PHP Object Injection, CWE-502)
Critical Also affects pimcore/pimcore
GHSA-2mhj-fhvg-v428
Pimcore: ClassDefinition UID regex missing end anchor allows SQL injection via Block.php unquoted table name
High Also affects pimcore/pimcore
GHSA-7p36-fq2r-4h7r
Pimcore CMS Twig Sandbox Bypass via SecurityPolicy checkMethodAllowed
High Also affects pimcore/pimcore
GHSA-jwcc-gv4m-93x6
Pimcore has a CustomReports Share Bypass
High Also affects pimcore/pimcore
GHSA-332x-r494-54fq
Pimcore has a WordExport Authorization Bypass for Unauthorized Document Export
Medium Also affects pimcore/pimcore
GHSA-wc7j-g8wx-m2qx
Pimcore: Missing Authorization in WebDAV MOVE via unchecked asset move handling
High Also affects pimcore/pimcore
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