Crawl4AI before 0.9.5 Denial of Service via Unbounded CrawlerRunConfig Delay Fields
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.9.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Crawl4AI, an open-source web crawling tool, is affected in versions before 0.9.5, specifically its Docker API server. An unauthenticated attacker can send oversized delay settings to the crawl endpoints, tying up browser pages and stalling the rate limiter so that legitimate crawls are blocked.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Crawl4AI before 0.9.5 contains a denial of service vulnerability in the Docker API server where _clamp_untrusted() fails to cap the delay_before_return_html, mean_delay, and max_range fields of untrusted CrawlerRunConfig bodies. Unauthenticated attackers can send huge values to /crawl or /crawl/stream to hold browser pages or stall the rate limiter, exhausting the page pool and blocking other crawls.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- unclecode crawl4ai
fixed in 0.9.5