{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6867 exists.","fix":"No fix has been published for CVE-2024-6867 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-6867 is a medium-severity missing authorization vulnerability in Lunary Lunary, published on 13 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-6867 and fix it if it is affected.\n\nWhat it is: CVE-2024-6867 is a medium-severity missing authorization vulnerability in Lunary Lunary, published on 13 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6867 exists.\n\nAffected product: Lunary Lunary. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-6867/ (Markdown: https://insights.sbomify.com/CVE-2024-6867/index.md)","id":"CVE-2024-6867","markdown":"https://insights.sbomify.com/CVE-2024-6867/index.md","name":"CVE-2024-6867","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Lunary AI platform","requires_auth":"low_privilege","summary":"Attackers can access private run data via the related runs endpoint due to missing authorization checks, exposing sensitive information.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"lunary","vendor":"lunary"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-1220","name":"Insufficient Granularity of Access Control"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Information Disclosure in lunary-ai/lunary","id":"CVE-2024-6867","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"lunary:lunary","products":["lunary:lunary"],"type":"missing_authorization","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Arbitrary File Write in mudler/LocalAI","id":"CVE-2024-6868"},"packages":[],"prev":{"headline":"Case-Insensitive Path Matching in corydolphin/flask-cors","id":"CVE-2024-6866"},"products":["lunary-ai/lunary"],"published":"2024-09-13","related":[{"cvss_score":9.8,"headline":"Improper Access Control in lunary-ai/lunary","id":"CVE-2024-8999","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":9.8,"headline":"Improper Authorization in lunary-ai/lunary","id":"CVE-2024-9095","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":9.8,"headline":"SQL Injection in lunary-ai/lunary","id":"CVE-2024-7456","kev_date_added":null,"published":"2024-11-01"},{"cvss_score":9.8,"headline":"Incorrect Authorization in lunary-ai/lunary","id":"CVE-2024-4146","kev_date_added":null,"published":"2024-06-08"},{"cvss_score":9.6,"headline":"Account Hijacking via Password Reset Token Leak in lunary-ai/lunary","id":"CVE-2024-5386","kev_date_added":null,"published":"2026-02-02"},{"cvss_score":9.6,"headline":"Incorrect Authorization in lunary-ai/lunary","id":"CVE-2024-3379","kev_date_added":null,"published":"2024-11-14"},{"cvss_score":9.4,"headline":"IDOR Vulnerability in lunary-ai/lunary","id":"CVE-2024-5128","kev_date_added":null,"published":"2024-06-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-13","vendors":["lunary-ai"]},"summary":"Attackers can access private run data via the related runs endpoint due to missing authorization checks, exposing sensitive information.","url":"https://insights.sbomify.com/CVE-2024-6867/"}