Flow Bugfix Releases for Entity Security in typo3/flow
Summary
GHSA-vh6j-wv25-8qxr: Flow Bugfix Releases for Entity Security. Affects typo3/flow across 5 version ranges.
>= 3.0.0, < 3.0.12
>= 3.1.0, < 3.1.10
>= 3.2.0, < 3.2.13
>= 3.3.0, < 3.3.13
>= 4.0.0, < 4.0.6
Fixed in 5 releases; the minimum fixed version depends on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
typo3/flow is an open-source PHP web application framework that follows the Model-View-Controller (MVC) architectural pattern. It provides a flexible and extensible platform for developing web applications. The entity security feature in typo3/flow allows developers to secure entities based on user roles and other user properties. However, a vulnerability was discovered in the interaction between entity security and the doctrine query cache. This vulnerability could result in users seeing entities that were not intended for them, as SQL queries from the cache could be reused for different users.
Vulnerability Detail
The vulnerability in typo3/flow's entity security and doctrine query cache interaction allows for the exposure of sensitive data. When using entity security based on user properties, such as the company a user belongs to, the vulnerability arises. Due to improper handling of the doctrine query cache, SQL queries built for one user can be reused by other users, leading to the display of entities that should not be accessible to them. This can result in unauthorized access to sensitive data and a breach of data confidentiality.
How To Fix
Fixed versions by release line
The minimum fixed version depends on the release line you run.
-
>= 3.0.0, < 3.0.123.0.12composer require typo3/flow:3.0.12 -
>= 3.1.0, < 3.1.103.1.10composer require typo3/flow:3.1.10 -
>= 3.2.0, < 3.2.133.2.13composer require typo3/flow:3.2.13 -
>= 3.3.0, < 3.3.133.3.13composer require typo3/flow:3.3.13 -
>= 4.0.0, < 4.0.64.0.6composer require typo3/flow:4.0.6
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. It is recommended to update to the latest bugfix release as mentioned in the 'how_to_fix' section.
Conclusion
The vulnerability in typo3/flow's entity security and doctrine query cache interaction can lead to unauthorized access to sensitive data. It is crucial to update to the latest bugfix release to ensure the proper handling of this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for typo3/flow →
FAQ
typo3/flow is an open-source PHP web application framework that follows the Model-View-Controller (MVC) architectural pattern. It provides a flexible and extensible platform for developing web applications.
Entity security in typo3/flow allows developers to secure entities based on user roles and other user properties. It ensures that only authorized users can access specific entities.
The vulnerability allows unauthorized users to view entities that are not intended for them. This can result in the exposure of sensitive data and a breach of data confidentiality.
To fix this vulnerability, update typo3/flow to the latest bugfix release mentioned in the 'how_to_fix' section.
No specific workaround is mentioned for this vulnerability. It is recommended to update to the latest bugfix release.
References
Related vulnerabilities
Recent vulnerabilities recorded for typo3/flow.
