CVE-2024-5130 json
Incorrect Authorization in lunary-ai/lunary
published 2y ago modified 4mo ago also EUVD-2024-46387
- cvss
- 7.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
An Incorrect Authorization vulnerability exists in lunary-ai/lunary versions up to and including 1.2.2, which allows unauthenticated users to delete any dataset. The vulnerability is due to the lack of proper authorization checks in the dataset deletion endpoint. Specifically, the endpoint does not verify if the provided project ID belongs to the current user, thereby allowing any dataset to be deleted without proper authentication. This issue was fixed in version 1.2.8.
Patch / fix
- lunary-ai lunary-ai/lunary 1.2.8
- lunary-ai lunary 1.2.8
Is CVE-2024-5130 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
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.48% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- huntr.com https://huntr.com/bounties/e81a9871-308d-4628-9726-af66643a16fe 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
References
-
github.com
/lunary-ai/lunary/commit/14078c1d2b8766075bf655f187ece24c7a787776
patch
-
huntr.com
/bounties/e81a9871-308d-4628-9726-af66643a16fe
exploit, issue-tracking, patch, third-party-advisory
Sources
- CVE List CVE-2024-5130
- NVD CVE-2024-5130
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.