GHSA-vh6j-wv25-8qxr: Flow Bugfix Releases for Entity Security
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.
Published Jun 5, 2024
Affected packages
typo3/flow
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.0.0, < 3.0.12
- Fixed in
- 3.0.12
- Check
composer show typo3/flow
typo3/flow
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.1.0, < 3.1.10
- Fixed in
- 3.1.10
- Check
composer show typo3/flow
typo3/flow
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.2.0, < 3.2.13
- Fixed in
- 3.2.13
- Check
composer show typo3/flow
typo3/flow
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.3.0, < 3.3.13
- Fixed in
- 3.3.13
- Check
composer show typo3/flow
typo3/flow
- Ecosystem
- Composer (PHP)
- Affected
- >= 4.0.0, < 4.0.6
- Fixed in
- 4.0.6
- Check
composer show typo3/flow
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
