{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3760 exists.","fix":"No fix has been published for CVE-2024-3760 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-3760 is a high-severity denial of service vulnerability in Lunary Lunary, published on 14 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-3760 and fix it if it is affected.\n\nWhat it is: CVE-2024-3760 is a high-severity denial of service vulnerability in Lunary Lunary, published on 14 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3760 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-3760/ (Markdown: https://insights.sbomify.com/CVE-2024-3760/index.md)","id":"CVE-2024-3760","markdown":"https://insights.sbomify.com/CVE-2024-3760/index.md","name":"CVE-2024-3760","record":{"aliases":["GHSA-qqwx-8prm-3682"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Lunary AI platform","requires_auth":"none","summary":"Attackers can flood user mailboxes and overwhelm mail servers by exploiting missing rate limits on the password reset page, causing service disruption.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"lunary","vendor":"lunary"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"In lunary-ai/lunary version 1.2.7, there is a lack of rate limiting on the forgot password page, leading to an email bombing vulnerability. Attackers can exploit this by automating forgot password requests to flood targeted user accounts with a high volume of password reset emails. This not only overwhelms the victim's mailbox, making it difficult to manage and locate legitimate emails, but also significantly impacts mail servers by consuming their resources. The increased load can cause performance degradation and, in severe cases, make the mail servers unresponsive or unavailable, disrupting email services for the entire organization.","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":"Email Bombing Vulnerability in lunary-ai/lunary","id":"CVE-2024-3760","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"lunary:lunary","products":["lunary:lunary"],"type":"denial_of_service","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Missing Authorization on Delete Datasets in lunary-ai/lunary","id":"CVE-2024-3761"},"packages":[],"prev":{"headline":"Hmdfs has a use after free vulnerability","id":"CVE-2024-3759"},"products":["lunary-ai/lunary"],"published":"2024-11-14","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-18","vendors":["lunary-ai"]},"summary":"Attackers can flood user mailboxes and overwhelm mail servers by exploiting missing rate limits on the password reset page, causing service disruption.","url":"https://insights.sbomify.com/CVE-2024-3760/"}