# GHSA-w8qp-hmh5-4v9v: Object state limitation has no effect

> Attackers can bypass object state limitations to access restricted content, affecting applications using this specific access control feature.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Apr 2022

## What is GHSA-w8qp-hmh5-4v9v?

GHSA-w8qp-hmh5-4v9v is a missing authorization vulnerability in ezsystems/ezplatform-kernel, published on 29 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

## Which versions are affected by GHSA-w8qp-hmh5-4v9v?

2 open source packages ship an affected version, including ezsystems/ezplatform-kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ezsystems/ezplatform-kernel` | Packagist | From 1.3.0 | 1.3.17 |
| `ezsystems/ezplatform-kernel` | Packagist | From 1.3.0 | 1.3.17 |

## How do I fix GHSA-w8qp-hmh5-4v9v?

Upgrade ezsystems/ezplatform-kernel to 1.3.17 or later.

## Is GHSA-w8qp-hmh5-4v9v being exploited?

There is no known exploitation of GHSA-w8qp-hmh5-4v9v in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-w8qp-hmh5-4v9v and fix it if it is affected.

What it is: GHSA-w8qp-hmh5-4v9v is a missing authorization vulnerability in ezsystems/ezplatform-kernel, published on 29 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-w8qp-hmh5-4v9v in the wild and no public exploit code.

Affected packages and fixed versions:
- ezsystems/ezplatform-kernel (Packagist): affected from 1.3.0; fixed in 1.3.17
- ezsystems/ezplatform-kernel (Packagist): affected from 1.3.0; fixed in 1.3.17

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-w8qp-hmh5-4v9v/ (Markdown: https://insights.sbomify.com/GHSA-w8qp-hmh5-4v9v/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-w8qp-hmh5-4v9v

---
From sbomify Insights: https://insights.sbomify.com/GHSA-w8qp-hmh5-4v9v/
Summaries are generated and may contain mistakes; the official description above is the record.