Skip to content

Company admin role gives excessive privileges in eZ Platform Ibexa

High severity GitHub Reviewed Published Mar 12, 2023 to the GitHub Advisory Database • Updated Mar 16, 2023

Package

composer ezsystems/ezplatform-kernel (Composer)

Affected versions

>= 1.3.0, < 1.3.26

Patched versions

1.3.26
composer ezsystems/ezpublish-kernel (Composer)
>= 7.5.0, < 7.5.30
7.5.30

Description

Users with the Company admin role (introduced by the company account feature in v4) can assign any role to any user. This also applies to any other user that has the role / assign policy. Any subtree limitation in place does not have any effect.

The role / assign policy is typically only given to administrators, which limits the scope in most cases, but please verify who has this policy in your installaton. The fix ensures that subtree limitations are working as intended.

References

Published by the National Vulnerability Database Mar 12, 2023
Published to the GitHub Advisory Database Mar 12, 2023
Reviewed Mar 13, 2023
Last updated Mar 16, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.159%
(53rd percentile)

Weaknesses

CVE ID

CVE-2022-48365

GHSA ID

GHSA-qq2j-9pf8-g58c

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.