{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-5186 exists.","fix":"No fix has been published for CVE-2024-5186 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-5186 is a high-severity server-side request forgery vulnerability in imartinez/privategpt, published on 6 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-5186 and fix it if it is affected.\n\nWhat it is: CVE-2024-5186 is a high-severity server-side request forgery vulnerability in imartinez/privategpt, published on 6 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-5186 exists.\n\nAffected product: imartinez/privategpt. 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-5186/ (Markdown: https://insights.sbomify.com/CVE-2024-5186/index.md)","id":"CVE-2024-5186","markdown":"https://insights.sbomify.com/CVE-2024-5186/index.md","name":"CVE-2024-5186","record":{"aliases":["GHSA-p7p2-4qrf-46qf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"PrivateGPT application","requires_auth":"none","summary":"Attackers can exploit SSRF in file uploads to access internal networks and sensitive data via crafted path parameters.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"privategpt","vendor":"pribai"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A Server-Side Request Forgery (SSRF) vulnerability exists in the file upload section of imartinez/privategpt version 0.5.0. This vulnerability allows attackers to send crafted requests that could result in unauthorized access to the local network and potentially sensitive information. Specifically, by manipulating the 'path' parameter in a file upload request, an attacker can cause the application to make arbitrary requests to internal services, including the AWS metadata endpoint. This issue could lead to the exposure of internal servers and sensitive 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 imartinez/privategpt","id":"CVE-2024-5186","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Arbitrary File Overwrite in download_model_with_test_data in onnx/onnx","id":"CVE-2024-5187"},"packages":[],"prev":{"headline":"Data Poisoning in EmbedAI","id":"CVE-2024-5185"},"products":["imartinez/privategpt"],"published":"2024-06-06","related":[{"cvss_score":9.8,"headline":"Python Command Injection in imartinez/privategpt","id":"CVE-2024-4343","kev_date_added":null,"published":"2024-11-14"},{"cvss_score":7.5,"headline":"Denial of Service in imartinez/privategpt","id":"CVE-2024-12063","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":7.5,"headline":"Denial of Service (DOS) in imartinez/privategpt","id":"CVE-2024-8018","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":7.5,"headline":"Local File Inclusion in imartinez/privategpt","id":"CVE-2024-3403","kev_date_added":null,"published":"2024-05-16"},{"cvss_score":6.8,"headline":"Unrestricted File Upload Leading to XSS in imartinez/privategpt","id":"CVE-2024-3851","kev_date_added":null,"published":"2024-05-16"},{"cvss_score":5.4,"headline":"CSRF Vulnerability in imartinez/privategpt","id":"CVE-2024-5935","kev_date_added":null,"published":"2024-06-27"}],"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":["imartinez"]},"summary":"Attackers can exploit SSRF in file uploads to access internal networks and sensitive data via crafted path parameters.","url":"https://insights.sbomify.com/CVE-2024-5186/"}