Lunary Ai/Lunary
Approved changes feed: RSS · Atom
cpe:2.3:a:lunary-ai:lunary-ai\/lunary:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Lunary Ai (b8ab520b-5869-56bb-8f02-94405305398c) |
|---|---|
| Product | Lunary Ai/Lunary (cbbd32bd-1b59-520f-9845-6483684b95cf) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-7475 |
vulnerable | 2026-06-08 06:58:22.265669 |
Improper Access Control in lunary-ai/lunary
CRITICAL (9.1)
An improper access control vulnerability in lunary-ai/lunary version 1.3.2 allows an attacker to update the SAML configuration without authorization. This vulnerability can lead to manipulation of authentication processes, fraudulent login requests, and theft of user information. Appropriate access controls should be implemented to ensure that the SAML configuration can only be updated by authorized users.
Published: 2024-10-29T12:45:53.136Z
Updated: 2025-10-21T14:10:24.049Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-7456 |
vulnerable | 2026-06-08 06:58:22.220100 |
SQL Injection in lunary-ai/lunary
CRITICAL (9.8)
A SQL injection vulnerability exists in the `/api/v1/external-users` route of lunary-ai/lunary version v1.4.2. The `order by` clause of the SQL query uses `sql.unsafe` without prior sanitization, allowing for SQL injection. The `orderByClause` variable is constructed without server-side validation or sanitization, enabling an attacker to execute arbitrary SQL commands. Successful exploitation can lead to complete data loss, modification, or corruption.
Published: 2024-11-01T12:05:12.189Z
Updated: 2024-11-01T13:19:19.973Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-6867 |
vulnerable | 2026-06-08 06:58:20.620982 |
Information Disclosure in lunary-ai/lunary
MEDIUM (4.3)
An information disclosure vulnerability exists in the lunary-ai/lunary, specifically in the `runs/{run_id}/related` endpoint. This endpoint does not verify that the user has the necessary access rights to the run(s) they are accessing. As a result, it returns not only the specified run but also all runs that have the `run_id` listed as their parent run. This issue affects the main branch, commit a761d833. The vulnerability allows unauthorized users to obtain information about non-public runs and their related runs, given the `run_id` of a public or non-public run.
Published: 2024-09-13T16:13:02.869Z
Updated: 2024-09-13T16:38:51.331Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-6862 |
vulnerable | 2026-06-08 06:58:20.615223 |
Cross-Site Request Forgery (CSRF) in lunary-ai/lunary
HIGH (7.4)
A Cross-Site Request Forgery (CSRF) vulnerability exists in lunary-ai/lunary version 1.2.34 due to overly permissive CORS settings. This vulnerability allows an attacker to sign up for and create projects or use the instance as if they were a user with local access. The main attack vector is for instances hosted locally on personal machines, which are not publicly accessible. The CORS settings in the backend permit all origins, exposing unauthenticated endpoints to CSRF attacks.
Published: 2024-09-13T16:13:51.639Z
Updated: 2024-09-13T16:35:41.728Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-6582 |
vulnerable | 2026-06-08 06:58:19.942333 |
Broken Access Control in lunary-ai/lunary
MEDIUM (6.5)
A broken access control vulnerability exists in the latest version of lunary-ai/lunary. The `saml.ts` file allows a user from one organization to update the Identity Provider (IDP) settings and view the SSO metadata of another organization. This vulnerability can lead to unauthorized access and potential account takeover if the email of a user in the target organization is known.
Published: 2024-09-13T16:11:39.817Z
Updated: 2024-11-03T18:27:25.362Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-6087 |
vulnerable | 2026-06-08 06:58:17.723512 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-5755 |
vulnerable | 2026-06-08 06:56:17.282898 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-3760 |
vulnerable | 2026-06-08 06:43:51.400521 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-3502 |
vulnerable | 2026-06-08 06:41:53.481379 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-3501 |
vulnerable | 2026-06-08 06:41:53.480916 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-3379 |
vulnerable | 2026-06-08 06:41:53.090780 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1643 |
vulnerable | 2026-06-08 06:27:13.962711 | db.gcve.eu details were skipped to keep the page responsive. | 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.