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.
Scoring
- Severity
- HIGH
- CVSS base score
- 7.5
- CVSS vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- EPSS probability
- 0.39%
- CWE
- CWE-821
- Published
- 2024-04-10
- Last modified
- 2026-03-13
Affected products
- lunary-ai lunary-ai/lunary
Weakness type
Related vulnerabilities
- CVE-2026-77584 — Tor before 0.4.9.10 did not reject a CONFLUX_LINK cell that arrives on a circuit which already has...
- CVE-2026-56132 — In libexpat before 2.8.2, there is a heap-based buffer overflow in doProlog in xmlparse.c because...
- CVE-2026-21919 — Junos OS and Junos OS Evolved: A high frequency of connecting and disconnecting NETCONF sessions causes management unavailability
- CVE-2024-58133 — In chainmaker-go (aka ChainMaker) before 2.4.0, when making frequent updates to a node's...
- CVE-2024-58132 — In chainmaker-go (aka ChainMaker) before 2.3.6, multiple updates to a single node's configuration...
- CVE-2024-58131 — FISCO BCOS 3.11.0 has an issue with synchronization of the transaction pool that can, for example,...
- CVE-2024-6657 — BLE peripheral DoS after few cycles of connect/disconnects
- CVE-2024-4278 — Incorrect Synchronization in GitLab