{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11822 exists.","fix":"No fix has been published for CVE-2024-11822 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-11822 is a medium-severity server-side request forgery vulnerability in langgenius/dify, published on 20 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-11822 and fix it if it is affected.\n\nWhat it is: CVE-2024-11822 is a medium-severity server-side request forgery vulnerability in langgenius/dify, published on 20 Mar 2025. 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-11822 exists.\n\nAffected product: langgenius/dify. 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-11822/ (Markdown: https://insights.sbomify.com/CVE-2024-11822/index.md)","id":"CVE-2024-11822","markdown":"https://insights.sbomify.com/CVE-2024-11822/index.md","name":"CVE-2024-11822","record":{"aliases":["GHSA-8v6j-vg6w-6wwj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Dify AI platform","requires_auth":"low_privilege","summary":"Attackers can exploit improper api_endpoint handling to access internal network services and AWS metadata, exposing sensitive information.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"dify","vendor":"dify"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"langgenius/dify version 0.9.1 contains a Server-Side Request Forgery (SSRF) vulnerability. The vulnerability exists due to improper handling of the api_endpoint parameter, allowing an attacker to make direct requests to internal network services. This can lead to unauthorized access to internal servers and potentially expose sensitive information, including access to the AWS metadata endpoint.","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 langgenius/dify","id":"CVE-2024-11822","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Folder Gallery \u003c= 1.7.4 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2024-11823"},"packages":[],"prev":{"headline":"Privilege Escalation in langgenius/dify","id":"CVE-2024-11821"},"products":["langgenius/dify"],"published":"2025-03-20","related":[{"cvss_score":9.3,"headline":"Dify \u003c 1.14.2 Authorization Bypass via Trace Configuration Endpoints","id":"CVE-2026-41947","kev_date_added":null,"published":"2026-05-18"},{"cvss_score":9.3,"headline":"Dify v1.14.1 Path Traversal via Plugin Daemon Internal API Access","id":"CVE-2026-41948","kev_date_added":null,"published":"2026-05-18"},{"cvss_score":8.8,"headline":"Pandas Query Injection in langgenius/dify","id":"CVE-2025-0185","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8.7,"headline":"Dify \u003c 1.16.0-rc1 SQL Injection via MyScale Vector Store search_by_full_text","id":"CVE-2026-61461","kev_date_added":null,"published":"2026-07-10"},{"cvss_score":8.4,"headline":"Dify Vulnerable to Plaintext API Key Exposure via Model Provider Configuration Endpoint","id":"CVE-2025-67732","kev_date_added":null,"published":"2026-01-05"},{"cvss_score":8.2,"headline":"Dify \u003c 1.14.2 Authorization Bypass via File Preview Endpoint","id":"CVE-2026-41949","kev_date_added":null,"published":"2026-05-18"}],"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":"2025-03-20","vendors":["langgenius"]},"summary":"Attackers can exploit improper api_endpoint handling to access internal network services and AWS metadata, exposing sensitive information.","url":"https://insights.sbomify.com/CVE-2024-11822/"}