GHSA-9cw3-j7wg-jwj8

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

Cette page présente des faits issus de sources publiques. Consultez l’avis original avant toute mise à jour.

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.

CVSS 4.3 · Moyenne · Correctif disponible

Publication

2024-05-17T22:54:45Z

Mise à jour

2024-12-02T05:43:02.925009Z

Pile logicielle: php

Vérifiez votre serveur →