lunary-ai lunary up to 0.x PATCH Request /v1/projects/:projectId unnecessary privileges
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in lunary-ai lunary up to 0.x. It has been classified as critical. Affected is an unknown function of the file /v1/projects/:projectId of the component PATCH Request Handler. Performing a manipulation results in unnecessary privileges. This vulnerability was named CVE-2024-1626. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability was found in lunary-ai lunary up to 0.x. It has been classified as critical. This affects an unknown code block of the file /v1/projects/:projectId of the component PATCH Request Handler. The manipulation with an unknown input leads to a unnecessary privileges vulnerability. CWE is classifying the issue as CWE-250. The product performs an operation at a privilege level that is higher than the minimum level required, which creates new weaknesses or amplifies the consequences of other weaknesses. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An Insecure Direct Object Reference (IDOR) vulnerability exists in the lunary-ai/lunary repository, version 0.3.0, within the project update endpoint. The vulnerability allows authenticated users to modify the name of any project within the system without proper authorization checks, by directly referencing the project's ID in the PATCH request to the '/v1/projects/:projectId' endpoint. This issue arises because the endpoint does not verify if the provided project ID belongs to the currently authenticated user, enabling unauthorized modifications across different organizational projects.
The advisory is shared at huntr.com. This vulnerability is uniquely identified as CVE-2024-1626 since 02/19/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 1.0.0 eliminates this vulnerability. Applying the patch 9eb9e526edff8bf82ae032f7a04867c8d58572bc is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Product: https://github.com/lunary-ai/lunary/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.2VulDB Meta Temp Score: 8.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.1
NVD Vector: 🔍
CNA Base Score: 9.1
CNA Vector (huntr.dev): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Unnecessary privilegesCWE: CWE-250
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: lunary 1.0.0
Patch: 9eb9e526edff8bf82ae032f7a04867c8d58572bc
Timeline
02/19/2024 🔍04/16/2024 🔍
04/16/2024 🔍
01/10/2025 🔍
Sources
Product: github.comAdvisory: 9eb9e526edff8bf82ae032f7a04867c8d58572bc
Status: Confirmed
CVE: CVE-2024-1626 (🔍)
GCVE (CVE): GCVE-0-2024-1626
GCVE (VulDB): GCVE-100-260853
Entry
Created: 04/16/2024 08:12Updated: 01/10/2025 15:47
Changes: 04/16/2024 08:12 (67), 05/23/2024 08:18 (1), 01/10/2025 15:47 (12)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.