crawl4ai@0.8.7

🚀🤖 Crawl4AI: Open-source LLM Friendly Web Crawler & scraper

  • latest version

    0.9.0

  • latest non vulnerable version

  • first published

    1 years ago

  • latest version published

    12 days ago

  • licenses detected

  • Direct Vulnerabilities

    Known vulnerabilities in the crawl4ai package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • H
    Server-side Request Forgery (SSRF)

    Crawl4AI is a 🚀🤖 Crawl4AI: Open-source LLM Friendly Web Crawler & scraper

    Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the handle_stream_crawl_request process. An attacker can access internal-only services and cloud-metadata endpoints by sending crafted requests to the affected API endpoints, causing the server to fetch and stream responses from arbitrary internal URLs.

    How to fix Server-side Request Forgery (SSRF)?

    Upgrade Crawl4AI to version 0.9.0 or higher.

    [,0.9.0)
    • H
    Symlink Attack

    Crawl4AI is a 🚀🤖 Crawl4AI: Open-source LLM Friendly Web Crawler & scraper

    Affected versions of this package are vulnerable to Symlink Attack via the download process. An attacker can overwrite arbitrary files with attacker-controlled content by supplying crafted filenames containing absolute paths or directory traversal sequences, which are then written outside the intended downloads directory. This can lead to execution of malicious code by overwriting files such as shell rc-files, ~/.ssh/authorized_keys, cron entries, or Python modules on the import path. This is only exploitable if the crawler is run with sufficient privileges or in an environment where sensitive paths are writable.

    How to fix Symlink Attack?

    Upgrade Crawl4AI to version 0.9.0 or higher.

    [,0.9.0)
    • C
    Arbitrary Code Injection

    Crawl4AI is a 🚀🤖 Crawl4AI: Open-source LLM Friendly Web Crawler & scraper

    Affected versions of this package are vulnerable to Arbitrary Code Injection via the browser_config.extra_args parameter in API requests. An attacker can execute arbitrary commands as the container's runtime user by injecting malicious Chromium launch arguments, leading to full read/write access to application data, secrets, environment variables, and potential data exfiltration. This is only exploitable if the Docker API server is left unauthenticated and accessible to attackers.

    How to fix Arbitrary Code Injection?

    Upgrade Crawl4AI to version 0.9.0 or higher.

    [,0.9.0)
    • H
    Server-side Request Forgery (SSRF)

    Crawl4AI is a 🚀🤖 Crawl4AI: Open-source LLM Friendly Web Crawler & scraper

    Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the proxy_config.server parameter in the browser_config or crawler_config objects, as well as related proxy settings in extra_args. An attacker can access internal services and cloud-metadata endpoints by supplying a proxy address pointing to internal IPs, causing the server to route requests through attacker-controlled proxies and return sensitive responses.

    How to fix Server-side Request Forgery (SSRF)?

    Upgrade Crawl4AI to version 0.8.9 or higher.

    [,0.8.9)
    • C
    Improper Output Neutralization for Logs

    Crawl4AI is a 🚀🤖 Crawl4AI: Open-source LLM Friendly Web Crawler & scraper

    Affected versions of this package are vulnerable to Improper Output Neutralization for Logs via the output_path parameter in the Docker API server's screenshot and PDF endpoints, which failed to properly resolve symlinks and allowed file writes outside the intended directory. An attacker can achieve arbitrary file writes, potentially leading to code execution, by supplying crafted symlinked paths. Additionally, user-controlled input was reflected into log lines and webhook headers without adequate sanitization, enabling log forging and injection of unauthorized headers in outbound webhook requests. This is only exploitable if the API is left unauthenticated or the runtime user has write access to sensitive locations.

    How to fix Improper Output Neutralization for Logs?

    Upgrade Crawl4AI to version 0.8.8 or higher.

    [,0.8.8)
    • H
    Server-side Request Forgery (SSRF)

    Crawl4AI is a 🚀🤖 Crawl4AI: Open-source LLM Friendly Web Crawler & scraper

    Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the validate_webhook_url and validate_url_destination functions. An attacker can access internal services and cloud metadata endpoints by submitting specially crafted URLs that encode internal IP addresses using IPv6 transition forms or unspecified addresses. This is only exploitable if the API server is left unauthenticated (with jwt_enabled: false).

    How to fix Server-side Request Forgery (SSRF)?

    Upgrade Crawl4AI to version 0.8.8 or higher.

    [,0.8.8)
    • H
    Server-side Request Forgery (SSRF)

    Crawl4AI is a 🚀🤖 Crawl4AI: Open-source LLM Friendly Web Crawler & scraper

    Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the base_url parameter in API requests and the resolution of environment variables in the LLM configuration process. An attacker can obtain sensitive server-held secrets, such as provider API keys or authentication tokens, by supplying a malicious base_url or referencing protected environment variables in the request.

    How to fix Server-side Request Forgery (SSRF)?

    Upgrade Crawl4AI to version 0.8.8 or higher.

    [,0.8.8)