Bypasses / SSRF protection
SSRF protection
68 cases that got past this protection.
- QuantumNous/new-api has an SSRF Filter Bypass via 0.0.0.0 Using 0.0.0.0 as the host in multimodal image URLs slips past new-api's private IP filter, so the server fetches localhost.
- PraisonAI has an SSRF bypass The URL validator checks the host that urlparse extracts, but requests connects to a different host for crafted backslash and at-sign URLs, reaching internal addresses.
- langchain-openai: Image token counting SSRF protection can be bypassed via DNS rebinding Image URLs are validated for private addresses and then fetched separately, so DNS rebinding lets the fetch reach internal hosts despite the check.
- LangChain Text Splitters: HTMLHeaderTextSplitter.split_text_from_url SSRF Redirect Bypass URL validation runs only on the first request, and redirects are then followed without revalidation, so an attacker can reach internal or metadata endpoints.
- Flowise: SSRF Protection Bypass (TOCTOU & Default Insecure) DNS rebinding exploits the gap between a validation lookup and the connection lookup, and the default empty deny list lets requests reach localhost.
- Flowise Execute Flow function has an SSRF vulnerability The Execute Flow node's base URL is not checked by the deny-list validator, so the server issues requests to internal addresses.
- Flowise: SSRF Protection Bypass via Direct node-fetch / axios Usage (Patch Enforcement Failure) Several tools call raw HTTP clients directly instead of the centralised SSRF wrapper, so requests to internal addresses still succeed.
- Flowise: SSRF Protection Bypass via Unprotected Built-in HTTP Modules in Custom Function Sandbox Custom function code can load built-in http, https or net modules that bypass the SSRF deny list, reaching internal services such as cloud metadata endpoints.
- vLLM has SSRF Protection Bypass vLLM's URL check parses backslash-containing URLs differently from the aiohttp client that fetches them, letting a request reach an attacker host.
- Gradio has SSRF via Malicious `proxy_url` Injection in `gr.load()` Config Processing A malicious remote Space config adds its own proxy host to the allowlist, letting the victim's server reach internal addresses.
- LangChain Community: redirect chaining can lead to SSRF bypass via RecursiveUrlLoader The URL check in RecursiveUrlLoader runs only on the starting address, so automatic redirects can send the crawler to internal or metadata endpoints.
- @langchain/community affected by SSRF Bypass in RecursiveUrlLoader via insufficient URL origin validation Crawled pages can link to hosts whose names merely start with the base domain or to private and metadata addresses, which the crawler fetches without validation.
- vLLM vulnerable to Server-Side Request Forgery (SSRF) through MediaConnector Host restrictions in the media loader parse backslashes differently in two libraries, so a crafted URL can reach internal hosts.
- new-api is vulnerable to SSRF Bypass A redirect from an allowed external URL points the server at internal addresses, because the SSRF check only validates the first request.
- lobe-chat implemented an insufficient fix for GHSA-mxhq-xw3g-rphc (CVE-2024-32964) The proxy's SSRF check validates only the initial URL and ignores redirects, so an external URL can redirect the server to private or loopback addresses.
- MindsDB Vulnerable to Bypass of SSRF Protection with DNS Rebinding The private-address check resolves the hostname once, so a DNS record that later returns an internal address redirects the real request to internal services.
- langchain Server-Side Request Forgery vulnerability An attacker-controlled page links to other domains, and the crawler follows them despite the setting meant to keep it on the original site.
- Label Studio SSRF on Import Bypassing `SSRF_PROTECTION_ENABLED` Protections The URL import validates the target with one DNS lookup, so redirects or DNS rebinding let requests reach internal hosts despite the SSRF setting.