GHSA-w4xc-px5p-c32w: Crawl4AI before 0.9.5 Blind SSRF via CacheValidator Freshness Check
Crawl4AI before 0.9.5 contains a blind server-side request forgery vulnerability in the Docker server that allows API clients to bypass the egress proxy by enabling checkcachefreshness. Attackers can cache a controlled URL, then trigger CacheValidator to follow 302 redirects or DNS rebinding to internal and cloud-metadata addresses for port and service discovery.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Crawl4AIto a version that resolves this vulnerability.Fixed in 0.9.5
Frequently Asked Questions
Which deployments are exposed?
Deployments running the Crawl4AI Docker server before 0.9.5 are affected when API clients can enable check_cache_freshness. The issue is reached through the server's cache freshness validation path.
What does an attacker need to do to exploit this issue?
An attacker needs to cache a controlled URL and then trigger CacheValidator through check_cache_freshness. They can use HTTP 302 redirects or DNS rebinding to cause requests to internal services or cloud-metadata addresses.
How can I determine whether remediation is needed?
Check whether the Crawl4AI Docker server is running a version earlier than 0.9.5 and whether API clients can use check_cache_freshness. Systems meeting both conditions should be treated as affected.