CVE-2024-11301: Improper Enforcement of Unique Constraint in lunary-ai/lunary
lunary-ai · lunary-ai/lunary
Fixed in 1.6.3 · Affected: lunary-ai/lunary before 1.6.3 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 48% of scored CVEs
DescriptionCVE.org
In lunary-ai/lunary before version 1.6.3, the application allows the creation of evaluators without enforcing a unique constraint on the combination of projectId and slug. This allows an attacker to overwrite existing data by submitting a POST request with the same slug as an existing evaluator. The lack of database constraints or application-layer validation to prevent duplicates exposes the application to data integrity issues. This vulnerability can result in corrupted data and potentially malicious actions, impairing the system's functionality.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- lunary-ai · lunary-ai/lunarybefore 1.6.3
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- lunary-ai
- Published
- March 2025
CoverageNo articles yet
No CyberSIXT article names CVE-2024-11301 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.