CVE-2024-1902

lunary-ai/lunary is vulnerable to a session reuse attack, allowing a removed user to change the organization name without proper authorization. The vulnerability stems from the lack of validation to check if a user is still part of an organization before allowing them to make changes. An attacker can exploit this by using an old authorization token to send a PATCH request, modifying the organization's name even after being removed from the organization. This issue is due to incorrect synchronization and affects the orgs.patch route.

lunary-ai/lunary is vulnerable to a session reuse attack, allowing a removed user to change the organization name without proper authorization. The vulnerability stems from the lack of validation to check if a user is still part of an organization before allowing them to make changes. An attacker can exploit this by using an old authorization token to send a PATCH request, modifying the organization's name even after being removed from the organization. This issue is due to incorrect synchronization and affects the orgs.patch route.

lunary-ai/lunary es vulnerable a un ataque de reutilización de sesión, lo que permite que un usuario eliminado cambie el nombre de la organización sin la autorización adecuada. La vulnerabilidad surge de la falta de validación para verificar si un usuario todavía es parte de una organización antes de permitirle realizar cambios. Un atacante puede aprovechar esto utilizando un token de autorización antiguo para enviar una solicitud PATCH, modificando el nombre de la organización incluso después de haber sido eliminada de ella. Este problema se debe a una sincronización incorrecta y afecta la ruta orgs.patch.