Lunary 1.2.13
Approved changes feed: RSS · Atom
cpe:2.3:a:lunary:lunary:1.2.13:*:*:*:*:*:*:*part: a version: 1.2.13 update: *
| Vendor | Lunary (d06a62eb-8728-5903-8388-539ff39c70e6) |
|---|---|
| Product | Lunary (8681bafc-d844-59ba-bfe1-ff3e7976ea73) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from NVD CPE 2.0 feed
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/lunary-ai/lunary |
purl2cpe | 2026-06-01 10:12:14.765488 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-5389 |
vulnerable | 2026-06-08 06:56:15.783727 |
Insufficient Access Control in lunary-ai/lunary
MEDIUM (5.7)
In lunary-ai/lunary version 1.2.13, an insufficient granularity of access control vulnerability allows users to create, update, get, and delete prompt variations for datasets not owned by their organization. This issue arises due to the application not properly validating the ownership of dataset prompts and their variations against the organization or project of the requesting user. As a result, unauthorized modifications to dataset prompts can occur, leading to altered or removed dataset prompts without proper authorization. This vulnerability impacts the integrity and consistency of dataset information, potentially affecting the results of experiments.
Published: 2024-06-09T22:22:38.179Z
Updated: 2024-08-01T21:11:12.487Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-4146 |
vulnerable | 2026-06-08 06:50:17.110027 |
Incorrect Authorization in lunary-ai/lunary
CRITICAL (9.8)
In lunary-ai/lunary version v1.2.13, an incorrect authorization vulnerability exists that allows unauthorized users to access and manipulate projects within an organization they should not have access to. Specifically, the vulnerability is located in the `checkProjectAccess` method within the authorization middleware, which fails to adequately verify if a user has the correct permissions to access a specific project. Instead, it only checks if the user is part of the organization owning the project, overlooking the necessary check against the `account_project` table for explicit project access rights. This flaw enables attackers to gain complete control over all resources within a project, including the ability to create, update, read, and delete any resource, compromising the privacy and security of sensitive information.
Published: 2024-06-08T19:41:25.437Z
Updated: 2024-08-30T15:28:58.378Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.