{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-5885 exists.","fix":"No fix has been published for CVE-2024-5885 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-5885 is a high-severity server-side request forgery vulnerability in stangirard/quivr, published on 27 Jun 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-5885 and fix it if it is affected.\n\nWhat it is: CVE-2024-5885 is a high-severity server-side request forgery vulnerability in stangirard/quivr, published on 27 Jun 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-5885 exists.\n\nAffected product: stangirard/quivr. 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-5885/ (Markdown: https://insights.sbomify.com/CVE-2024-5885/index.md)","id":"CVE-2024-5885","markdown":"https://insights.sbomify.com/CVE-2024-5885/index.md","name":"CVE-2024-5885","record":{"aliases":["GHSA-x34h-5qgf-76hx"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Quivr web application","requires_auth":"none","summary":"An attacker can exploit SSRF in Quivr to access internal network resources and cloud metadata endpoints.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"quivr","vendor":"quivr"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"stangirard/quivr version 0.0.236 contains a Server-Side Request Forgery (SSRF) vulnerability. The application does not provide sufficient controls when crawling a website, allowing an attacker to access applications on the local network. This vulnerability could allow a malicious user to gain access to internal servers, the AWS metadata endpoint, and capture Supabase data.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Server-Side Request Forgery (SSRF) in stangirard/quivr","id":"CVE-2024-5885","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2024-5886"},"packages":[],"prev":{"headline":"Beauty \u003c= 1.1.4 - Authenticated (Subscriber+) Stored Cross-Site Scripting via tpl_featured_cat_id Parameter","id":"CVE-2024-5884"},"products":["stangirard/quivr"],"published":"2024-06-27","related":[{"cvss_score":7.7,"headline":"SSRF Vulnerability in stangirard/quivr","id":"CVE-2024-4851","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":6.8,"headline":"Stored XSS in stangirard/quivr","id":"CVE-2024-6229","kev_date_added":null,"published":"2024-07-07"},{"cvss_score":4.3,"headline":"Path Traversal in stangirard/quivr","id":"CVE-2024-6583","kev_date_added":null,"published":"2025-03-20"}],"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-08-01","vendors":["stangirard"]},"summary":"An attacker can exploit SSRF in Quivr to access internal network resources and cloud metadata endpoints.","url":"https://insights.sbomify.com/CVE-2024-5885/"}