GHSA-vh6j-wv25-8qxr Flow Bugfix Releases for Entity Security
Not scored
Published
Check this codebase for GHSA-vh6j-wv25-8qxr and fix it if it is affected.
What it is: GHSA-vh6j-wv25-8qxr is a vulnerability in typo3/flow, published on 5 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-vh6j-wv25-8qxr in the wild and no public exploit code.
Affected packages and fixed versions:
- typo3/flow (Packagist): affected from 3.0.0; fixed in 3.0.12
- typo3/flow (Packagist): affected from 3.0.0; fixed in 3.0.12
- typo3/flow (Packagist): affected from 3.1.0; fixed in 3.1.10
- typo3/flow (Packagist): affected from 3.1.0; fixed in 3.1.10
- typo3/flow (Packagist): affected from 3.2.0; fixed in 3.2.13
- typo3/flow (Packagist): affected from 3.2.0; fixed in 3.2.13
- typo3/flow (Packagist): affected from 3.3.0; fixed in 3.3.13
- typo3/flow (Packagist): affected from 3.3.0; fixed in 3.3.13
- typo3/flow (Packagist): affected from 4.0.0; fixed in 4.0.6
- typo3/flow (Packagist): affected from 4.0.0; fixed in 4.0.6
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-vh6j-wv25-8qxr/ (Markdown: https://insights.sbomify.com/GHSA-vh6j-wv25-8qxr/index.md)
Improper cache handling in entity security allows authenticated users to view data belonging to other users.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-vh6j-wv25-8qxr?
GHSA-vh6j-wv25-8qxr is a vulnerability in typo3/flow, published on 5 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
If you had used entity security and wanted to secure entities not just based on the user's role, but on some property of the user (like the company he belongs to), entity security did not work properly together with the doctrine query cache. This could lead to other users re-using SQL queries from the cache which were built for other users; and thus users could see entities which were not destined for them.
Which versions are affected by GHSA-vh6j-wv25-8qxr?
10 open source packages ship an affected version, including typo3/flow.
| Package | Affected | Fixed in |
|---|---|---|
typo3/flow Packagist | From 3.0.0 | 3.0.12 |
typo3/flow Packagist | From 3.0.0 | 3.0.12 |
typo3/flow Packagist | From 3.1.0 | 3.1.10 |
typo3/flow Packagist | From 3.1.0 | 3.1.10 |
typo3/flow Packagist | From 3.2.0 | 3.2.13 |
typo3/flow Packagist | From 3.2.0 | 3.2.13 |
4 more packages
typo3/flow Packagist | From 3.3.0 | 3.3.13 |
typo3/flow Packagist | From 3.3.0 | 3.3.13 |
typo3/flow Packagist | From 4.0.0 | 4.0.6 |
typo3/flow Packagist | From 4.0.0 | 4.0.6 |
How do I fix GHSA-vh6j-wv25-8qxr?
Upgrade typo3/flow to a fixed version for your release line: 3.0.12, 3.1.10, 3.2.13 or 3.3.13.
Is GHSA-vh6j-wv25-8qxr being exploited?
There is no known exploitation of GHSA-vh6j-wv25-8qxr in the wild and no public exploit code.