NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Composer (PHP)

GHSA-9cw3-j7wg-jwj8: Neos Flow Information disclosure in entity security

mediumCVSS 3.1 4.3

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 May 17, 2024

Affected packages

neos/flow

Ecosystem
Composer (PHP)
Affected
>= 3.0.0, < 3.0.12
Fixed in
3.0.12
Check
composer show neos/flow

neos/flow

Ecosystem
Composer (PHP)
Affected
>= 3.1.0, < 3.1.10
Fixed in
3.1.10
Check
composer show neos/flow

neos/flow

Ecosystem
Composer (PHP)
Affected
>= 3.2.0, < 3.2.13
Fixed in
3.2.13
Check
composer show neos/flow

neos/flow

Ecosystem
Composer (PHP)
Affected
>= 3.3.0, < 3.3.13
Fixed in
3.3.13
Check
composer show neos/flow

neos/flow

Ecosystem
Composer (PHP)
Affected
>= 4.0.0, < 4.0.6
Fixed in
4.0.6
Check
composer show neos/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.

Am I affected?

  • Do you use Entity Security? if no, you are not affected.
  • You disabled the Doctrine Cache (Flow_Persistence_Doctrine)? If this is the case, you are not affected.
  • You use Entity Security in custom Flow or Neos applications. Read on.
  • If you only used Entity Security based on roles (i.e. role A was allowed to see entities, but role B was denied): In this case, you are not affected.
  • If you did more advanced stuff using Entity Security (like checking that a customer only sees his own orders; or a hotel only sees its own bookings), you very likely needed to register a custom global object in Neos.Flow.aop.globalObjects. In this case, you are affected by the issue; and need to implement the CacheAwareInterface in your global object for proper caching.

All Flow versions (starting in version 3.0, where Entity Security was introduced) were affected.

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

More Composer (PHP) vulnerabilities

All Composer (PHP) entries