CVE-2024-1902 json
Session Reuse Vulnerability in lunary-ai/lunary
published 2024-04-10 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-17624
- cvss
- 7.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- lunary-ai lunary-ai/lunary 1.2.8
- lunary-ai lunary 1.2.8
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.com https://huntr.com/bounties/e536310e-abe7-4585-9cf6-21f77390a5e8 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected products
- lunary-ai lunary-ai/lunary
- lunary-ai lunary
Classification
- Weakness
-
- CWE-821 Incorrect Synchronization
References
-
github.com
/lunary-ai/lunary/commit/d8e2e73efd53ab4e92cf47bbf4b639a9f08853d2
patch
-
huntr.com
/bounties/e536310e-abe7-4585-9cf6-21f77390a5e8
exploit, issue-tracking, patch, third-party-advisory
Sources
- CVE List CVE-2024-1902
- NVD CVE-2024-1902
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.