CVE-2024-12779
SSRF in Infiniflow Ragflow 0.12.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2024-12779 is a high-severity SSRF (CWE-918) vulnerability in Infiniflow Ragflow. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
This vulnerability is AI-related — categorised as LLM Application Platforms; in the Supply Chain and Deployment risk domain.
The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-12779 is a Server-Side Request Forgery (SSRF) vulnerability affecting infiniflow/ragflow version 0.12.0. The issue resides in the POST /v1/llm/add_llm and POST /v1/conversation/tts endpoints, where attackers can specify an arbitrary URL as the api_base parameter when adding an OPENAITTS model. This allows subsequent requests to the tts REST API endpoint to fetch and read contents from the attacker-controlled URL. The vulnerability is rated with a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) and is associated with CWE-918.
Any unauthenticated attacker with network access to the vulnerable RAGFlow instance can exploit this SSRF by first submitting a request to add an LLM model with a malicious api_base URL pointing to internal or restricted resources. They can then trigger the tts endpoint to proxy requests to that URL, enabling them to read sensitive data such as internal web services, metadata endpoints, or other backend resources inaccessible from the internet. This results in high confidentiality impact without requiring privileges, user interaction, or elevated complexity.
Details on the vulnerability, including potential patches or workarounds, are documented in advisories from the Huntr bug bounty program at https://huntr.com/bounties/3cc748ba-2afb-4bfe-8553-10eb6d6dd4f0.
RAGFlow is a framework for retrieval-augmented generation (RAG) workflows involving large language models (LLMs), making this SSRF particularly relevant in AI/ML deployment environments where internal LLM APIs or data stores may be exposed. No public information on real-world exploitation is available as of the CVE publication on 2025-03-20.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-7013
Vulnerability Data
A Server-Side Request Forgery (SSRF) vulnerability exists in infiniflow/ragflow version 0.12.0. The vulnerability is present in the `POST /v1/llm/add_llm` and `POST /v1/conversation/tts` endpoints. Attackers can specify an arbitrary URL as the `api_base` when adding an `OPENAITTS` model, and subsequently access…
more
the `tts` REST API endpoint to read contents from the specified URL. This can lead to unauthorized access to internal web resources.
- CWE(s)
AI Security AnalysisAI
- AI Category
- LLM Application Platforms
- Risk Domain
- Supply Chain and Deployment
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: llm
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.6V1.5.3V5.3.2V10.4.7
Mitigating Controls (NIST 800-53 r5) AI
Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.
Input validation directly stops untrusted URLs from being accepted and fetched without destination checks.
Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure development practices directly include input validation and destination allow-listing that prevent SSRF.
Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.
Vulnerability identification processes can discover and record SSRF flaws in web applications.
Network segmentation and egress controls can limit the damage from successful SSRF requests.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Operational threat data describing SSRF campaigns can be used to tighten outbound-request allow-lists and detection rules before attackers exploit them.