First published: Wed Apr 10 2024(Updated: )
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.
Credit: security@huntr.dev
Affected Software | Affected Version | How to fix |
---|---|---|
lunary lunary | <1.2.8 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-1902 is rated as a high severity vulnerability due to its potential to allow unauthorized changes.
To fix CVE-2024-1902, implement user validation checks to verify that a user is still part of the organization before allowing changes.
CVE-2024-1902 affects all versions of lunary prior to 1.2.8.
CVE-2024-1902 enables session reuse attacks where a removed user can change the organization name without authorization.
The main cause of CVE-2024-1902 is a lack of validation for user organization membership before allowing changes.