{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4851 exists.","fix":"No fix has been published for CVE-2024-4851 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-4851 is a high-severity server-side request forgery vulnerability in stangirard/quivr, published on 6 Jun 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-4851 and fix it if it is affected.\n\nWhat it is: CVE-2024-4851 is a high-severity server-side request forgery vulnerability in stangirard/quivr, published on 6 Jun 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-4851 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-4851/ (Markdown: https://insights.sbomify.com/CVE-2024-4851/index.md)","id":"CVE-2024-4851","markdown":"https://insights.sbomify.com/CVE-2024-4851/index.md","name":"CVE-2024-4851","record":{"aliases":["GHSA-rcfg-x28g-p9m3"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Quivr application","requires_auth":"low_privilege","summary":"Attackers can exploit an SSRF vulnerability in the crawl endpoint to access internal networks and services via manipulated URL parameters.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"quivr","vendor":"quivr"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A Server-Side Request Forgery (SSRF) vulnerability exists in the stangirard/quivr application, version 0.0.204, which allows attackers to access internal networks. The vulnerability is present in the crawl endpoint where the 'url' parameter can be manipulated to send HTTP requests to arbitrary URLs, thereby facilitating SSRF attacks. The affected code is located in the backend/routes/crawl_routes.py file, specifically within the crawl_endpoint function. This issue could allow attackers to interact with internal services that are accessible from the server hosting the application.","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":"SSRF Vulnerability in stangirard/quivr","id":"CVE-2024-4851","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Mismatched Memory Management Routines in editcap","id":"CVE-2024-4853"},"packages":[],"prev":{"headline":"WordPress Automatic \u003c= 3.94.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via autoplay Parameter","id":"CVE-2024-4849"},"products":["stangirard/quivr"],"published":"2024-06-06","related":[{"cvss_score":8.6,"headline":"Server-Side Request Forgery (SSRF) in stangirard/quivr","id":"CVE-2024-5885","kev_date_added":null,"published":"2024-06-27"},{"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-09","vendors":["stangirard"]},"summary":"Attackers can exploit an SSRF vulnerability in the crawl endpoint to access internal networks and services via manipulated URL parameters.","url":"https://insights.sbomify.com/CVE-2024-4851/"}