GHSA-394j-x37r-2q27 json
Ibexa DXP users with the Company admin role can assign any role to any user
published 4y ago modified last yr.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Critical severity. 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.
Patch / fix
Is GHSA-394j-x37r-2q27 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | ibexa/core | >=4.2.0, <4.2.3 |
4.2.3 |
References
-
github.com
/ibexa/core/commit/da3642c98d2c94607bb53ed2e42654eb92b42e17
web
-
github.com
/ibexa/core/security/advisories/GHSA-394j-x37r-2q27
web
-
developers.ibexa.co
/security-advisories/ibexa-sa-2022-009-critical-vulnerabilities-in-graphql-role-assignment-ct-editing-and-draf
web
-
github.com
/ibexa/core
package
Sources
- GitHub Advisory GHSA-394j-x37r-2q27
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.