CVE-2024-4154 json
Incorrect Synchronization in lunary-ai/lunary
published 2y ago modified 4mo ago also EUVD-2024-32713
- cvss
- 7.1
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
In lunary-ai/lunary version 1.2.2, an incorrect synchronization vulnerability allows unprivileged users to rename projects they do not have access to. Specifically, an unprivileged user can send a PATCH request to the project's endpoint with a new name for a project, despite not having the necessary permissions or being assigned to the project. This issue allows for unauthorized modification of project names, potentially leading to confusion or unauthorized access to project resources.
Patch / fix
- lunary-ai lunary-ai/lunary 1.2.26
Is CVE-2024-4154 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- huntr.com https://huntr.com/bounties/e56509af-f7af-4e1e-a04b-9cb53545f30f referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.1 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected products
- lunary-ai lunary-ai/lunary
- lunary-ai lunary
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
- github.com /lunary-ai/lunary/commit/c43b6c62035f32ca455f66d5fd22ba661648cde7
-
huntr.com
/bounties/e56509af-f7af-4e1e-a04b-9cb53545f30f
exploit, issue-tracking, patch, third-party-advisory
Sources
- CVE List CVE-2024-4154
- NVD CVE-2024-4154
Fencer Intel 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.