GHSA-w8qp-hmh5-4v9v
GHSA-w8qp-hmh5-4v9v · Object state limitation has no effect
This page contains facts from public vulnerability sources. Check the original advisory before updating.
Object state limitation is a policy you can use in your roles to limit access to content based on specific object state values. Due to a flawed earlier update, these limitations were ineffective in releases made since February 16th 2022. They would grant access to the given content regardless of the object state. Depending on how your frontend is designed, knowing the URL to the content may or may not be required to access it. If you are using object state limitations in your roles, this issue is critical. Please apply the fix as soon as possible.
Fix available
- Published
- Updated
Stack: php
Affected products and versions
ezsystems/ezplatform-kernel Packagist
- Versions
- v1.3.0
- v1.3.1
- v1.3.1.1
- v1.3.10
- v1.3.11
- v1.3.12
- v1.3.13
- v1.3.14
- v1.3.15
- v1.3.16
- v1.3.2
- v1.3.3
- v1.3.4
- v1.3.5
- v1.3.6
- v1.3.7
- v1.3.8
- v1.3.9
- Affected ranges
- ECOSYSTEM: ≥ 1.3.0, < 1.3.17
Update to 1.3.17
Original sources
- https://github.com/ezsystems/ezplatform-kernel/security/advisories/GHSA-w8qp-hmh5-4v9v
- https://developers.ibexa.co/security-advisories/ibexa-sa-2022-004-ineffective-object-state-limitation-and-unauthenticated-fastly-purge
- https://github.com/ezsystems/ezplatform-kernel
- https://osv.dev/vulnerability/GHSA-w8qp-hmh5-4v9v