In lunary-ai/lunary version v1.2.13, an improper authorization vulnerability exists that allows unauthorized users to access and manipulate projects within an organization they should not have access to. Specifically, the vulnerability is located in the `checkProjectAccess` method within the authorization middleware, which fails to adequately verify if a user has the correct permissions to access a specific project. Instead, it only checks if the user is part of the organization owning the project, overlooking the necessary check against the `account_project` table for explicit project access rights. This flaw enables attackers to gain complete control over all resources within a project, including the ability to create, update, read, and delete any resource, compromising the privacy and security of sensitive information.
En lunary-ai/lunary versión v1.2.13, existe una vulnerabilidad de autorización inadecuada que permite a usuarios no autorizados acceder y manipular proyectos dentro de una organización a la que no deberían tener acceso. Específicamente, la vulnerabilidad se ubica en el método `checkProjectAccess` dentro del middleware de autorización, que no logra verificar adecuadamente si un usuario tiene los permisos correctos para acceder a un proyecto específico. En cambio, solo verifica si el usuario es parte de la organización propietaria del proyecto, pasando por alto la verificación necesaria en la tabla `account_project` para obtener derechos de acceso explícitos al proyecto. Esta falla permite a los atacantes obtener control total sobre todos los recursos dentro de un proyecto, incluida la capacidad de crear, actualizar, leer y eliminar cualquier recurso, comprometiendo la privacidad y seguridad de la información confidencial.
In lunary-ai/lunary version v1.2.13, an incorrect authorization vulnerability exists that allows unauthorized users to access and manipulate projects within an organization they should not have access to. Specifically, the vulnerability is located in the `checkProjectAccess` method within the authorization middleware, which fails to adequately verify if a user has the correct permissions to access a specific project. Instead, it only checks if the user is part of the organization owning the project, overlooking the necessary check against the `account_project` table for explicit project access rights. This flaw enables attackers to gain complete control over all resources within a project, including the ability to create, update, read, and delete any resource, compromising the privacy and security of sensitive information.
