crawl4ai < 0.8.9 - Server Side Request Forgery
Crawl4AI References: https://github.com/unclecode/crawl4ai/security/advisories/GHSA-6qhc-x826-342c Remediation: Update to version 0.8.9 or later.
10 assets checked · domain, subdomain, ipv4
Crawl4AI is an open-source LLM friendly web crawler & scraper. Prior to 0.8.9, the Docker API server applied its SSRF destination check to the crawl target URL only, not to the proxy address. An unauthenticated request could supply a proxy pointing at an internal IP and route the browser through it, reaching internal services and cloud-metadata endpoints, while using a perfectly valid crawl URL. The Docker API is unauthenticated by default. /crawl, /crawl/stream, and /crawl/job accept a browser_config (and crawler_config). The following all feed Chromium's egress and were unchecked: browser_config.proxy_config.server, browser_config.proxy (deprecated field), crawler_config.proxy_config.server, and --proxy-server / --proxy-pac-url / --proxy-bypass-list / --host-resolver-rules flags in browser_config.extra_args. This vulnerability is fixed in 0.8.9.
Crawl4AI References: https://github.com/unclecode/crawl4ai/security/advisories/GHSA-6qhc-x826-342c Remediation: Update to version 0.8.9 or later.
10 assets checked · domain, subdomain, ipv4
S4E maps published CVEs to scanners and forecasts the next disclosure window for your stack.
Create a free account →