lunary-ai lunary up to 1.4.9 runs/{run_id}/related insufficient granularity of access control

Summaryinfo

A vulnerability was found in lunary-ai lunary up to 1.4.9. It has been classified as problematic. This issue affects some unknown processing of the file runs/{run_id}/related. The manipulation leads to insufficient granularity of access control. This vulnerability is uniquely identified as CVE-2024-6867. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in lunary-ai lunary up to 1.4.9 and classified as problematic. This issue affects an unknown code block of the file runs/{run_id}/related. The manipulation with an unknown input leads to a insufficient granularity of access control vulnerability. Using CWE to declare the problem leads to CWE-1220. The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets. Impacted is confidentiality. The summary by CVE is:

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.

The advisory is shared at huntr.com. The identification of this vulnerability is CVE-2024-6867 since 07/17/2024. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available.

Upgrading to version 1.4.10 eliminates this vulnerability. Applying the patch 35afd4439464571eb016318cd7b6f85a162225ca 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.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Artificial Intelligence Software

Vendor

• lunary-ai

Name

• lunary

Version

• 1.4.0
• 1.4.1
• 1.4.2
• 1.4.3
• 1.4.4
• 1.4.5
• 1.4.6
• 1.4.7
• 1.4.8
• 1.4.9

License

• open-source

Website

• Product: https://github.com/lunary-ai/lunary/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion